panic: ialloc: dup alloc

[Petr Drobny]

Hallo All,

I would like to know what
is bad on HP 9000 C360 with
HP-UX 11.0 if message
"panic: ialloc:dup alloc" is
written to console and system
is rebooted. I don't know
what Hardware or Software is
bad HW, HDDs or RAMs ... ?

Thanks for Your help.

Petr Drobny

[Clemens van Everdingen]

Hi,

Basically what had happenned is that the HFS subsystem allocated a free inode structure but only to find that this inode is not free since i_mode is still set!

Now to find out which inode and which HW causes this we need to have a look in the Oldsyslog file on the system for more info.

Please check this an post the complete message.

C.

[Petr Drobny]

Thank You for Your help and
whole message from OLDsyslog
is following:
vmunix: mode = 040770, inum = 4331162, fs = /t5, ip = 0x01a4d990
vmunix:
vmunix: linkstamp: Fri Dec 14 21:04:00 MET 2001
vmunix: _release_version: @(#)B2352B/9245XB HP-UX (B.11.00) #1: Thu Nov 6 01:58:21 PST 1997
vmunix: __kern_ci_revision: $Header: kern_sequence.c,v 1.6.106.512 97/11/05 18:01:46 msosa Exp $
vmunix: panic: ialloc: dup alloc
vmunix: PC-Offset Stack Trace (read across, top of stack is 1st):vmunix: 0x00253f34 0x001446f4 0x0013c61c 0x000a0ea4 0x0007c47c 0x001367d4

It seems as file system
"/t5" - but what would be
happend when file system
"/t5" is on disc array RAID 5
and this seems good ?

Thank You

Petr Drobny
PS: Im sorry, my English is too little

[Clemens van Everdingen]

Hi,

Yes it is /t5 filesystem.
You could check with fsck to see it gives some error's.
Could be a hw error, mirror error, fs corruption, file system could have been full.

C.

[Rainer von Bongartz]

Try locating the referenced inode

vmunix: mode = 040770, inum = 4331162, fs = /t5, ip = 0x01a4d990 #



find /t5 | xargs ls -li {} \; | grep 4331162

Regards
Rainer