On Mon, May 02, 2005 at 03:38:49AM +0100, Steven Hartland wrote: > Seems like doing a shutdown -p now on the current > 5.4-STABLE branch is resulting in FS corruption. > I've done this 4 times now and all but 1 time the > machine has failed to boot with a panic: > mod=0100600, inum=1271817, fs=/var > panic: ffs_valloc: dup alloc > cpuid = 0 > boot() called on cpu#0 > > The only way to fix is single user mode and manually > run fsck. Even the one time it didn't cause a panic I > still got a warning about / not being clean which it > should have been as the machine shutdown cleanly > no outstanding buffers.
In some cases fsck will not repair all corruption in one pass. Rerun it until it stops finding new things to fix. > Could this change have something to do with the panic > happening instead of just recovering? Doesn't seem likely to me. > Why would FS's be being corrupted by "shutdown -p now" where > as "reboot" doesnt seem to? Maybe the machine is being powered down before your disks have finished writing their data to disk. Kris
pgpaBsPVTiD90.pgp
Description: PGP signature
