Philip Guenther, 26 Oct 2014 14:23: > From the backtrace, either a bogus block number ended up in a > single-indirect block, or the filesystem superblock was corrupted. Or > something is scrambling memory. I think you're correct that this > filesystem has been damaged by whatever memory corruption you've been > experiencing beyond the point fsck handles. Time to backup, newfs, > reinstall and restore. And if you're still seeing memory corruptions > then maybe roll back to a version that didn't experience those and see > if you can bisect to whatever change caused the problem.
done and done, reinstalled. for the time being, can i minimize panic related fs errors by mounting using `sync` flag? -f -- i could prove god statistically. -- george gallup
