From: Timo Sirainen <tss@iki.fi>
To: Theodore Tso <tytso@mit.edu>
Cc: Josef Bacik <josef@toxicpanda.com>, linux-kernel@vger.kernel.org
Subject: Re: ext3/ext4 directories don't shrink after deleting lots of files
Date: Fri, 15 May 2009 13:29:04 -0400 [thread overview]
Message-ID: <1242408544.6933.687.camel@timo-desktop> (raw)
In-Reply-To: <20090515105815.GD6816@mit.edu>
[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]
On Fri, 2009-05-15 at 06:58 -0400, Theodore Tso wrote:
> > I was rather thinking something that I could run while the system was
> > fully operational. Otherwise just moving the files to a temp directory +
> > rmdir() + rename() would have been fine too.
> >
> > I just tested that xfs, jfs and reiserfs all shrink the directories
> > immediately. Is it more difficult to implement for ext* or has no one
> > else found this to be a problem?
>
> It's probably fairest to say no one has thought it worth the effort.
My problem is with mail servers and Maildir format where it's possible
that a user has tons of emails and wants to delete them. The mailbox
maybe slowly grows back to the huge size, but in the meantime it's
slower than necessary.
I can't really fix those directories while the system is running because
mail reading doesn't use any locking (and adding locking would be
unnecessary overhead). Writing does use locking though, so I could
create a new duplicate directory and switch it with the original
directory. But I suppose there's no way to atomically replace (or swap)
a non-empty directory with another?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-05-15 17:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 22:02 ext3/ext4 directories don't shrink after deleting lots of files Timo Sirainen
2009-05-15 0:32 ` Josef Bacik
2009-05-15 0:45 ` Timo Sirainen
2009-05-15 10:58 ` Theodore Tso
2009-05-15 17:29 ` Timo Sirainen [this message]
2009-05-15 18:25 ` Theodore Tso
2009-05-16 9:42 ` david
2009-05-17 21:33 ` Theodore Tso
2009-05-18 2:49 ` david
2009-05-18 3:21 ` Theodore Tso
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=1242408544.6933.687.camel@timo-desktop \
--to=tss@iki.fi \
--cc=josef@toxicpanda.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox