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.
Dan Price wrote:
On Tue 15 Nov 2005 at 03:50PM, Dennis Clarke wrote:
I just saw this :
fsck -F ufs -Y /dev/rdsk/c0t0** /dev/dsk/c0t0d0s0
** Currently Mounted on /
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3a - Check Connectivity
** Phase 3b - Verify Shadows/ACLs
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cylinder Groups
FILESYSTEM MAY STILL BE INCONSISTENT.
5331 files, 134218 used, 356643 free (539 frags, 44513 blocks, 0.1%
fragmentation)
***** FILE SYSTEM IS BAD *****
***** PLEASE RERUN FSCK *****
I didn't see those new 3a and 3b stages before. That is interesting.
I did rerun fsck again and I get the same message over and over. I
suspect that something else must be happening here. I may boot with
the cdrom just to verify.
--
Sean Wilcox
OP/N1 RPE - Data
Direct: (303) 272-9711
x79711
_______________________________________________
opensolaris-discuss mailing list
[email protected]
