Re: panic: ffs_valloc: dup alloc

[David Holland <dholland-current%netbsd.org@localhost>]

On Wed, Apr 11, 2012 at 08:34:07PM +0200, Manuel Bouyer wrote:
 > Hello,
 > ftp.fr.netbsd.org started panicing with:
 > dmode a40 mode a40 dgen 0 gen 0
 > size 0 blocks 0
 > ino 125737 ipref 131866
 > panic: ffs_valloc: dup alloc
 > 
 > fsck woulnd't find any issue on filesystems; after fsck the system would 
 > panic
 > shortly with the exact same message (same inode number). I would get the same
 > panic with a 5.1_STABLE and 6.0_BETA kernel (the problem first showed up
 > with the 6.0_BETA kernel). A 'clri 125737' from fsdb seems to have fixed the
 > issue (fsdb also showed the inode as unallocated).
 > 
 > does this ring a bell to someone ?

ffsv2?

There have been issues in the past with the lazy inode initialization
logic.

-- 
David A. Holland
dholland%netbsd.org@localhost