Files system problem again!!

[tristan308]

Filesystem was growing rapidly. Ran fsck on the filesystem and it came back with bad inode map & bad block map. Took system down unmounted filesystem then remounted, brought system back up. Ran fsck again, everything was fine. Plus did df -k and the file system went from 79% to 6%. Okay, that was Monday, now filesystem is at 11% and did the fsck on the filesystem and I get this again:

** Checking /dev/whateverlv (/whate) MOUNTED FILE SYSTEM; WRITING SUPPRESSED;
Checking a mounted filesystem does not produce dependable results.
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Inode Map
Bad Inode Map (NOT SALVAGED)
** Phase 6 - Check Block Map
Bad Block Map (NOT SALVAGED)
0 blocks missing
0 blocks missing
Filesystem integrity is not guaranteed
897 files 836696 blocks 7453504 free

Any solutions??

 

[vickersdc]

Is there anything in the error log..?

 

[tristan308]

The only thing in the error log is the cluster shuting down when we took the system down. Nothing new in it. Also nothing new in the filesystem that would indicate growth.

 

[tristan308]

Great!! Now I try to run fsck on the file system and I can't even get the output that I recieved from above. Anyone want to buy RS6000!!!!!!!!!!! ahhh

 

[bi]

Here are some suggestions. I don't know if you have tried any of this.

First, back up the files in the filesystem. Unmount the filesystem and run fsck on it. With the filesystem unmounted, fsck should try to repair the problems it found. Remount the filesystem and see if your problems are solved.

If they aren't, I'd recommend rebuilding the filesystem and restoring the backup to the new filesystem.

Good luck and let us know what happens.

 

[tcorum]

The only thing that seems to be missing in what you said above was that the filesystem each time you ran fsck was still mounted. You may have just typo'ed so ignore this if you did. If not then I have had the same problems. When you start having problems with the inodes you must unmount the filesystem then run fsck on it. If you run fsck two or three times in a row after mounting and unmounting it never seems to bring back the same data twice because of the inode errors. The size always seems to be much more than what you are actually using.

Solution: unmount the filesystem select yes when it asks you to repair the inodes and then remount it. If this does not work then its time to think about creating a new filesystem and moving your data.

Hope this helps,

Tcorum