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:

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

>Is the clri command from fsdb the same as /sbin/clri?

fsdb uses the code from fsck_ffs when it clears an inode,
which is to set all fields to zero.

clri also restores and increments the inode generation number,
that might help if an NFS client has cached it.

In either case the filesystem is dirty and you should
force a filesystem check. The journaling code has no
knowledge about such manual interventions.