On Sun, Oct 26, 2014 at 7:27 AM, frantisek holop <min...@obiit.org> wrote: > memtest did not reveal errors. > > unfortunately i got another panic, > during some routine file operations. > > (after the 2 previous panics, fsck > required manual running, and even > multiple runs, so maybe this one > is choking on fsck's best efforts, > i dont know.) > > savecore: reboot after panic: ffs_blkfree: bad size
>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. Philip Guenther
