Re: hammer-inodes: malloc limit exceeded

[Matthias Schmidt <matthias@xxxxxxxxxxxxxxxx>]

Hi,

* Francois Tigeot wrote:
> 
> I have just encountered this panic:
> 
> panic: hammer-inodes: malloc limit exceeded

I have encountered the same panic on one of my machines running HAMMER
here:

panic: hammer-inodes: malloc limit exceededmp_lock = 00000000; cpuid = 0
Trace beginning at frame 0xdf0b1a20
panic(df0b1a44,c03f67c0,ff80048c,248,df0b1a68) at panic+0x142
panic(c039cecf,c03a501c,0,11,ff800000) at panic+0x142
kmalloc(248,c03f67c0,102,db54f000,c02e3a62) at kmalloc+0xa5
hammer_create_inode(df0b1ac0,df0b1b5c,de4efa88,e268b738,0) at
hammer_create_inode+0x26hammer_vop_ncreate(df0b1b00,c03eab70,c41090b8,0,0)
at hammer_vop_ncreate+0x72
vop_ncreate(c41090b8,df0b1c84,e157a9b8,df0b1c08,de4efa88) at
vop_ncreate+0x3d
vn_open(df0b1c84,d746e638,603,1a4,c410ecf8) at vn_open+0xf3
kern_open(df0b1c84,602,1b6,df0b1cf0,ec0636c8) at kern_open+0x84
sys_open(df0b1cf0,c192e8,0,da362b78,c03db85c) at sys_open+0x32
syscall2(df0b1d40) at syscall2+0x240
Xint0x80_syscall() at Xint0x80_syscall+0x36
Debugger("panic")

CPU0 stopping CPUs: 0x00000002
 stopped
panic: from debugger
mp_lock = 00000000; cpuid = 0
boot() called on cpu#0
Uptime: 20d22h48m26s

dumping to dev #ad/0x20051, blockno 4269104
dump 
Fatal double fault:
eip = 0xc03733f1
esp = 0xdf0aefb0
ebp = 0xdf0af024
mp_lock = 00000000; cpuid = 0; lapic.id = 00000000
panic: double fault
mp_lock = 00000000; cpuid = 0
boot() called on cpu#0
Uptime: 20d22h48m26s
Dump already in progress, bailing...
spin_lock: 0xc4107d6c, indefinite wait!
spin_lock: 0xc4107d64, indefinite wait!
Shutting down ACPI
Automatic reboot in 15 seconds - press a key on the console to abort
--> Press a key on the console to reboot,
--> or switch off the system now.
Rebooting...

Unfortunately no crash dump :(  The machine is running HEAD from Tue Sep
30 11:47:27 CEST 2008.  It is a Intel C2D 3GHz with 2GB RAM running a
SMP kernel.  The fs layout is as follows:

ROOT                              292G    60G   232G    21%    /
/dev/ad10s1a                      252M   138M    94M    59%    /boot
/pfs/@@0xffffffffffffffff:00001   292G    60G   232G    21%    /usr
/pfs/@@0xffffffffffffffff:00003   292G    60G   232G    21%    /var
/pfs/@@0xffffffffffffffff:00006   292G    60G   232G    21%    /tmp
/pfs/@@0xffffffffffffffff:00007   292G    60G   232G    21%    /home
/pfs/@@0xffffffffffffffff:00005   292G    60G   232G    21%    /var/tmp
/pfs/@@0xffffffffffffffff:00002   292G    60G   232G    21%    /usr/obj
/pfs/@@0xffffffffffffffff:00004   292G    60G   232G    21%
/var/crash

The machine performed a pkgsrc "cvs update" before it crashed.  If more
information is needed, I'll provide it.  After the reboot kern.maxvnodes
is 129055 if that matters ...

Regards

	Matthias