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. In either case, its too late, I have booted via CDROM ( Solaris Express build 25 ) and am presently ufsdump'ing everything and then I will run a full surface scan of the disk sector by sector. If I am doing nothing but wasting my time .. well .. its too late now. At any rate, I will be able to re-create the critical filesystems with my own specs ( via mkfs_ufs ) and then ufsrestore from the dumps. There is a little voice in my head that whispers "zfs will make this all a distant memory" but what do I know. I have yet to see the specs for zfs. Dennis
_______________________________________________ opensolaris-discuss mailing list [email protected]
