* what does e2fsck's "non-contiguous" really say?
@ 2007-05-15 9:35 Tomasz Chmielewski
0 siblings, 0 replies; only message in thread
From: Tomasz Chmielewski @ 2007-05-15 9:35 UTC (permalink / raw)
To: linux-kernel
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2007-05-15 9:36 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-05-15 9:35 what does e2fsck's "non-contiguous" really say? Tomasz Chmielewski
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.