From: Theodore Tso <tytso@MIT.EDU>
To: Christian Kujau <lists@nerdbynature.de>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Eric Sandeen <sandeen@redhat.com>,
ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: e2fsprogs and fast symlink
Date: Mon, 24 Mar 2008 08:36:41 -0400 [thread overview]
Message-ID: <20080324123641.GH24943@mit.edu> (raw)
In-Reply-To: <alpine.DEB.1.00.0803241323350.4451@sheep.housecafe.de>
On Mon, Mar 24, 2008 at 01:25:33PM +0100, Christian Kujau wrote:
> Aneesh, can you elaborate a bit for me (a user, not a developer) what this
> means? I too had these "Fast symlink 12 has EXTENT_FL set. Clear<y>?"
> messages on my ext4 fs and I went on to "Clear" these things. Now I notice
> some serious performance (or better: load) problems when doing stuff on
> ext4 and I'm not sure if this could be related to the changes e2fsprogs
> did.
It should make no difference. The bug which Aneesh was pointing out
was that e2fsck was complaining about long symlinks in ext4 which got
deleted, and which thus got mistaken for fast symlinks with the
EXTENTS_FL flag set, even though said inodes were already deleted.
So this should not make any difference in terms of ext4 performance;
just noise in terms of needlessly annoying someone running e2fsck.
- Ted
next prev parent reply other threads:[~2008-03-24 12:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 11:42 e2fsprogs and fast symlink Aneesh Kumar K.V
2008-03-24 11:37 ` Aneesh Kumar K.V
2008-03-24 20:45 ` Andreas Dilger
2008-03-24 21:26 ` Theodore Tso
2008-03-25 0:40 ` Andreas Dilger
2008-03-24 12:20 ` [E2FSPROGS, PATCH] e2fsck: Don't object to extents flags on deleted fast symlinks Theodore Ts'o
2008-03-24 12:25 ` e2fsprogs and fast symlink Christian Kujau
2008-03-24 12:36 ` Theodore Tso [this message]
2008-03-24 13:18 ` Christian Kujau
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=20080324123641.GH24943@mit.edu \
--to=tytso@mit.edu \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=lists@nerdbynature.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox