panic: hammer_mount: malloc limit exceeded
Francois Tigeot
ftigeot at wolfpond.org
Tue Jun 10 14:36:07 PDT 2008
Hi,
I have just upgraded my machine to today's 1.13 (HAMMER 53G) and
re-created a test Hammer filesystem. I then ran cpdup to copy /home to
the new fs.
The exact command was: cpdup -I -v -i0 /home /home.hammer
Everything seemed to be ok at first. After about 1 hour, the kernel panicked.
Details of configuration:
Core 2 Duo, 2GB RAM
ad4: 400GB Western Digital WD4000YS
ad8: 500GB Western Digital WD5001ABYS (faster than ad4)
Filesystems after panic:
Filesystem Size Used Avail Capacity iused ifree %iused
Mounted on
/dev/ad8 466G 241G 187G 56% 196815 373807 34% /home
Home 347G 139G 208G 40% 78725 0 100% /home.hammer
/home.hammer is on ad4
Text of panic (recopied by hand):
panic: hammer_mount: malloc limit exceeded
mp_lock: 00000000; cpuid = 0
Trace beginning at frame 0xdc4aaabc
panic(dc4aaae0,0,0c04017e0,ff80048c,dc4aab08) at panic+0x14d
panic(c03a50ae,c03ae7c5,c40f1948,c42b2474,ff800000) at panic+0x14d
kmalloc(88,c04017e0,102,0,0) at kmalloc + 0xbb
hammer_alloc_mem_record(e6fb7d18,0,94000,0,2c9e634e) at hammer_alloc_mem_record + 0x22
hammer_ip_add_bulk(e6fb7d18,90000,0,c9248000,4000) at hammer_ip_add_bulk + 0x11c
hammer_vop_strategy(dc4aacb8,c03f6268,d3a0f510,c264b720,93000) at hammer_vop_strategy + 0x676
vop_strategy(d3a0f510,e000d18e8,c4435a48) at vop_strategy + 0x2c
vn_strategy(e000d18e8,c4435a48,c4435b30,c4435b30,4000) at vn_strategy + 0x50
bwrite(c4435a18) at bwrite + 0xfa
vfs_bio_awrite(c4435a18,c41b8ac0,ff800000,dc4aad84,c01f9f6e) at vfs_bio_awrite + 0x301
flushbufqueues(c41b89d0,0,c01b1a3,0,0) at flushbufqueues + 0x148
buf_daemon_hw(0,0,0,0,0) at buf_daemon_hw + 0x4f
kthread_exit() at kthread_exit
Debugger("panic")
CPU0 stopping: CPUs: 0x00000002
stopped
Stopped at Debugger + 0x34: movb $0,in_Debugger.4464
db>
I am fairly confident I can reproduce this given sufficient time.
--
Francois Tigeot
More information about the Bugs
mailing list