FILE SYSTEM STATE IN SUPERBLOCK IS WRONG; FIX?
yes 57893 files, 4084692 used, 11261835 free (4179 frags, 1407207 blocks, 0.0% frag mentation) ** /dev/rdsk/c1t2d0s0 ** Last Mounted on /u0 ** Phase 1 – Check Blocks and Sizes ** Phase 2 – Check Pathnames ** Phase 3 – Check Connectivity ** Phase 4 – Check Reference Counts ** Phase 5 – Check Cyl groups FILE SYSTEM STATE IN SUPERBLOCK IS WRONG; FIX?yes For the above filesystem it showed me 1.2% fragmentation. Later when I mounted the filesystems. It showed me 75% & later after some time it again showed me 100%. I really don’t know what should be done. Please give me some permanent solution. All the help is highly appreciated. Thanks in Advance.
The metastat command confirms that the transactional volume, d1, is in the “Okay” state. The file system is unmounted before detaching the transactional volume’s log device. The transactional volume and its mirrored master device are exchanged by using the -f (force) flag. Running the metastat command again confirms that the exchange occurred. The transactional volume and the log device (if desired) are cleared, in this case, d21 and d0, respectively. Next, the fsck command is run on the mirror, d1, and the prompt is answered with a y. After the fsck command is done, the file system is remounted. Note that because the mount device for /fs2 did not change, the /etc/vfstab file does not require editing.
In either case, type “yes” and press return. You should get a FILE SYSTEM WAS MODIFIED message. Reboot your system. If system complains about shutdown not being found do a halt -q. Now, hopefully, your system will boot up with out any problems. [Thanks to Kevin Smith.] Copyright 1997 – 2006 Dan Anderson. All rights reserved. http://sun.drydog.
