Re: Data loss after power out - fsck: bad inode number to nextinode

What should I do?

In theory,

clri {special-file} 306176

should wipe the inode containing the bad pointer and allow fsck to
continue, perhaps recovering the files pointed to by that directory
into lost+found.

Definitely try this on a copy first if at all possible.
freebsd-questions@xxxxxxxxxxx mailing list
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"