From: Chris Wedgwood <cw@f00f.org>
To: Alexander Viro <viro@math.psu.edu>
Cc: "Richard B. Johnson" <root@chaos.analogic.com>,
Steven Van Acker <deepstar@ulyssis.org>,
linux-kernel@vger.kernel.org,
"Stephen C. Tweedie" <sct@redhat.com>
Subject: Re: ext2 directory size bug (?)
Date: Sat, 2 Dec 2000 18:30:21 +1300 [thread overview]
Message-ID: <20001202183021.D412@metastasis.f00f.org> (raw)
In-Reply-To: <20001202175704.B269@metastasis.f00f.org> <Pine.GSO.4.21.0012020007270.27040-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0012020007270.27040-100000@weyl.math.psu.edu>; from viro@math.psu.edu on Sat, Dec 02, 2000 at 12:14:34AM -0500
On Sat, Dec 02, 2000 at 12:14:34AM -0500, Alexander Viro wrote:
Not really. Anything that modifies directories holds both ->i_sem and
->i_zombie, lookups hold ->i_sem and emptiness checks (i.e. victim in
rmdir and overwriting rename) hold ->i_zombie, readdir holds both.
what performance issues does this raise in the cast of a directory
with _many_ files in it -- when we are renaming often involving that
directory?
I ask this because certain MTAs do just that; and when you have
10,000 to 100,000 messages queued I immagine you might spend much of
your time waiting for ->i_sem locks?
Truncating is a piece of cake. Repacking is not a good idea,
though, since you are risking massive corruption in case of dirty
shutdown in the wrong moment.
ext2 directories seem somewhat susepctable to corruption on badly
timed shutdowns anyhow; and I don't think there is any way to do
atomic writes to them with most disk hardware is there?
--cw
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-02 6:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-30 4:17 ext2 directory size bug (?) Steven Van Acker
2000-11-30 7:20 ` Andreas Dilger
2000-11-30 13:24 ` Richard B. Johnson
2000-12-02 4:57 ` Chris Wedgwood
2000-12-02 5:14 ` Alexander Viro
2000-12-02 5:30 ` Chris Wedgwood [this message]
2000-12-02 5:42 ` Alexander Viro
2000-12-02 9:14 ` Kai Henningsen
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=20001202183021.D412@metastasis.f00f.org \
--to=cw@f00f.org \
--cc=deepstar@ulyssis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
--cc=sct@redhat.com \
--cc=viro@math.psu.edu \
/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.