On Sun, 28 Jul 2013, Frank Leonhardt wrote:

So it boils down to:

a) Leave is is, as it can detect when the kernel has trashed its vnode table; or

b) It's probably caused by "expected" FS corruption, so handle it gracefully.

It would be good to log a system error message like "filesystem may be corrupt" to give the user some clue other than a seemingly impossible error with no explanation.
freebsd-questions@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Reply via email to