-----Original Message-----
From: "Hylton Conacher (ZR1HPC)"
Having got to the point where I could run the fsck binary, I did so using the command: fsck -v -p -c -f /dev/hdb1 etc as listed in my /etc/fstab file, besides a few like the swap, usbdev.
Having the verbose mode on allowed me to see what details were displayed for each partition I ran it on. I noticed that on all the drives fsck'd they all had non=contiguous inodes percentages of anything from 0 to 15% if memory serves me.
Considering all the partitions I did were ext3 how come the nc inodes are so high? I thought with ext3 being a journaling fs they would all be 0? am I right in assuming that the nc inodes is similar to how much the partition is fragmented? I looked on Google for 'What are non-contiguous inodes' but there were just too many results not giving a direct answer to the question.
How do I recover the nc inodes or get the %'s to 0?
You don't ever get them to 0%. What makes 15% so high? With todays high speed disk drives fragmentation is not such a problem unless using MS that does not continously defrag the drive. That's why you don't readily see defrag software for unix systems. If you have fixed the partition problems using fsck just enjoy your system. Ken