Pete Carah <pete_at_altadena.net> writes: > 2. The other source of a panic is if the background fsck detects a condition > which would cause the "preen" fsck to abort and give the "run fsck manually" > message at bootup, it (usually?) panics the system, usually with "freeing > freed inode". I can't think of how to handle this case any better; this > is a "hobson's choice" condition :-( That can only happen in two ways. Either there is a bug in softupdates which prevents it from working correctly, or your disks are reporting data as written when it is in fact only in the write cache. -- Best regards Christian LaursenReceived on Sat Jan 17 2004 - 11:34:28 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:38 UTC