After a reboot due to a crash, fsck panic'ed on me with the following

dev = ad0s1a, ino = 270, fs = /
panic: ffs_vfree: freeing free inode

This was with a kernel of Dec 20. To be sure I compiled a new kernel and
world with recent sources but I still get the same panic with fsck.

The system is on a IDE disk and softupdates are enabled, I don't seem to
experience any data loss (if I skip the fsck at boot time).

Any ideas or suggestions on how to fix this are very welcome. Multiple
crashdumps are available.



Mark Santcroos                          RIPE Network Coordination Centre          New Projects Group/TTM

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to