On Tue, Nov 15, 2005 at 04:49:31PM -0500, Dennis Clarke wrote: > On 11/15/05, Sean Wilcox <[EMAIL PROTECTED]> wrote: > > This is because the filesystem is mounted read/write, and there > > is no way for fsck to 100% guarentee that the fs is sane after it > > has been run, especially with the -Y option, on a fs that is mounted > > read/write due to possible modification that might have tripped up > > fsck's ability to track things correctly. > > > > The Statement that the FILE SYSTEM IS BAD is probably a little too harsh > > but the FS INCONSISTENT statement could be true. > > Well, the ability to boot so single user mode and then run fsck on the > current root slice seems to be something that I have done for a long > long time. I think I may have to consider that one must now boot from > some other media in order to be assured of fs sanity.
You can always boot with '-m milestone=none', and run fsck from that environment; the root filesystem will be mounted read-only. In single-user mode, you might be able to re-mount the root filesystem read-only (mount -o ro,remount /), but I'm not sure that's supported. You could try to write-lock it using "lockfs -fw /", but I'm not sure that's well-advised. Cheers, - jonathan -- Jonathan Adams, Solaris Kernel Development _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
