From: Coly Li <colyli@gmail.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Andreas Dilger <adilger@clusterfs.com>, linux-ext4@vger.kernel.org
Subject: Re: What is fragment in ext3/4 ?
Date: Sat, 04 Aug 2007 00:20:38 +0800 [thread overview]
Message-ID: <46B355D6.8000007@gmail.com> (raw)
In-Reply-To: <46B35260.9000900@redhat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Eric Sandeen wrote:
> Andreas Dilger wrote:
>> On Aug 02, 2007 17:55 +0800, Coly Li wrote:
>>> These days, when I read the source code of mke2fs, I found an option -f
>>> to set the fragment size.
>>>
>>> But I can not find any explaining for ext3/4 framgment from google,
>>> excepting someone saying ext2/3 does not support this feature.
>>>
>>> Can anyone tell me what is the function or purpose of fragment of ext
>>> file system ?
>> This is an obsolete concept from BSD that was never used by ext[234].
>> Consider a "fragment" in this context to be the same as a "tail" for
>> reiserfs. A very small file, or the end of a file that is less than
>> a block.
>
> There's a fair amount of code around this never-implemented concept;
> should it be removed? :)
I agree with this idea. It seems we will never implement it in future,
once "fragment" packed into inode.
Coly
>
> -Eric
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iD8DBQFGs1XWuTp8cyZ5lTERAoFSAJsE4noHvOm77i0BKWiw5L1DDAnLKgCfXKcv
uL2ZZDiPJYUDWpKWwtIf1uo=
=bGt4
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-08-03 16:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 9:55 What is fragment in ext3/4 ? Coly Li
2007-08-03 0:02 ` Andreas Dilger
2007-08-03 9:15 ` Coly Li
2007-08-03 16:05 ` Eric Sandeen
2007-08-03 16:20 ` Coly Li [this message]
2007-08-03 22:28 ` Andreas Dilger
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=46B355D6.8000007@gmail.com \
--to=colyli@gmail.com \
--cc=adilger@clusterfs.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.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 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.