From: Tomasz Chmielewski <mangoo@wpkg.org>
To: linux-kernel@vger.kernel.org
Subject: what does e2fsck's "non-contiguous" really say?
Date: Tue, 15 May 2007 11:35:57 +0200 [thread overview]
Message-ID: <46497EFD.6050900@wpkg.org> (raw)
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
reply other threads:[~2007-05-15 9:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46497EFD.6050900@wpkg.org \
--to=mangoo@wpkg.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox