What does e2fsck's "non-contiguous" really say? I always thought it may
give a clue about how a filesystem is fragmented.
However, I had set up a filesystem on a 365 GB RAID-5 array:
/dev/sdao 365G 195M 347G 1% /mnt/1
The filesystem contains only one directory (lost+found).
I ran e2fsck on that filesystem, and it says "9.1% non-contiguous":
# e2fsck -f part
e2fsck 1.39 (29-May-2006)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
part: 11/48594944 files (9.1% non-contiguous), 1574757/97187200 blocks
"9.1% non-contiguous" - what meaning does it really have?
--
Tomasz Chmielewski
http://wpkg.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
