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
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
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
3 matches
Mail list logo