From: Theodore Tso <tytso@mit.edu>
To: Phillip Susi <psusi@cfl.rr.com>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Yea old defrag
Date: Wed, 22 Oct 2008 16:40:53 -0400 [thread overview]
Message-ID: <20081022204053.GA10369@mit.edu> (raw)
In-Reply-To: <48FF86AC.6060802@cfl.rr.com>
On Wed, Oct 22, 2008 at 04:01:48PM -0400, Phillip Susi wrote:
>
> I have been trying to identify any new features that cause problems and
> fix any that arise. Aren't extended attributes stored in the extra
> space of large inodes? If so, I would need to format a new fs using
> large inodes to test.
Extended attributes *can* be stored in the extra space of large
inodes, but they can also be stored in separate, stand-alone data
blocks --- and just to make life entertaining, if multiple files have
exactly the same set of extended attributes (for example, if all of
the files inone directory have the same ACL and/or SELinux property),
an extended attribute block can be shared across multiple inodes for
space efficiency.
> Are there any other ext3 features that might cause trouble? I know
> there are plenty in ext4, but I want to make sure everything works well
> in ext3 first.
That's probably the main one; and as you say, there are plenty of new
features that will require special handling for e2defrag, especially
since it doesn't use the standard libext2fs library.
- Ted
prev parent reply other threads:[~2008-10-22 20:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 16:10 Yea old defrag Phillip Susi
2008-10-22 18:03 ` Theodore Tso
2008-10-22 20:01 ` Phillip Susi
2008-10-22 20:40 ` Theodore Tso [this message]
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=20081022204053.GA10369@mit.edu \
--to=tytso@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=psusi@cfl.rr.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