Re: Repeated ffs_newvnode panic (dup alloc) on one inode

[mlelstv%serpens.de@localhost (Michael van Elst)]

anthony.mallet%laas.fr@localhost (Anthony Mallet) writes:

>fsdb (inum: 2)> inode 5242183
>current inode 5242183: unallocated inode

fsdb reports "unallocated inode" when the format bits of the mode are zero.
ffs panics when the mode is not zero.

>fs_newvnode: dup alloc ino=3D5242183 on /home: mode 142/142 gen 0/0 size 0 blocks

The mode is (octal) 142 != 0, so there is some garbage....

fsck should be able to clean the inode, you may need to force it when
it thinks the filesytem was clean.

So should the ancient tool clri. It's still a good idea to run fsck
afterwards.