From: Eric Sandeen <sandeen@redhat.com>
To: Andreas Dilger <adilger@sun.com>
Cc: zelogik+bugzilla@gmail.com, linux-ext4@vger.kernel.org
Subject: Re: [Bug 13930] New: non-contiguous files (64.9%) on a ext4 fs
Date: Fri, 07 Aug 2009 14:08:40 -0500 [thread overview]
Message-ID: <4A7C7BB8.2060904@redhat.com> (raw)
In-Reply-To: <20090807185853.GK3340@webber.adilger.int>
Andreas Dilger wrote:
> On Aug 07, 2009 09:58 +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
>> Normally ext4 is a perfect non-contifuous FS ... so why when I make an:
>>
>> sudo e2fsck -v -f -p /dev/sdc1
>>
>> 15953 inodes used (0.03%)
>> 10361 non-contiguous files (64.9%)
>>
>> We have 64.9% of non-contiguous files on a ext4 fs,
>>
>> Files have been transfered from a cifs mount (useful ?) and files size are
>> [2-10]|[600-800]MB
>
> Note that the largest single extent in ext4 is 128MB, so it is perfectly
> normal to have fragmented files if they are 600MB in size. Maybe we should
> change the e2fsck stats to not consider a file fragmented if it fills the
> whole block group (less any metadata therein)?
Ah that crossed my mind, but since so many other e2fsprogs tools
coalesce adjacent extents and report "1" I figured e2fsck was too
(though I didn't look...)
-Eric
next prev parent reply other threads:[~2009-08-07 19:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 9:58 [Bug 13930] New: non-contiguous files (64.9%) on a ext4 fs bugzilla-daemon
2009-08-07 14:40 ` [Bug 13930] " bugzilla-daemon
2009-08-07 18:58 ` [Bug 13930] New: " Andreas Dilger
2009-08-07 19:08 ` Eric Sandeen [this message]
2009-08-08 0:16 ` Theodore Tso
2009-08-07 22:20 ` [Bug 13930] " bugzilla-daemon
2009-08-07 22:38 ` bugzilla-daemon
2009-08-08 1:30 ` bugzilla-daemon
2009-08-10 12:04 ` bugzilla-daemon
2009-08-10 13:11 ` bugzilla-daemon
2009-10-19 5:55 ` bugzilla-daemon
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=4A7C7BB8.2060904@redhat.com \
--to=sandeen@redhat.com \
--cc=adilger@sun.com \
--cc=linux-ext4@vger.kernel.org \
--cc=zelogik+bugzilla@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).