From: Wang Sheng-Hui <shhuiw@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Eric Sandeen <sandeen@redhat.com>,
ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: Use fsck to free the space used by dir?
Date: Sat, 04 Aug 2012 12:25:49 +0800 [thread overview]
Message-ID: <501CA44D.2010201@gmail.com> (raw)
In-Reply-To: <20120803175727.GB8463@thunk.org>
On 2012年08月04日 01:57, Theodore Ts'o wrote:
> On Fri, Aug 03, 2012 at 10:18:57AM -0500, Eric Sandeen wrote:
>> On 8/3/12 9:19 AM, Wang Sheng-Hui wrote:
>>> Dear all,
>>>
>>> I read through the namei.c code recently, but didn't notice any code to
>>> reduce the size of a dir file (append can increase its size though).
>>
>> Right, AFAIK nothing in kernelspace will reduce the size.
>
> In theory, if the dir_index (htree) support is enabled, it would be
> possible for the kernel to reorganize the directory dynamically.
>
> If dir_index is not enabled, reorganizing the directory would would
> break any open readdir() sessions and any NFS server file handles.
> (Which means if the file system has been exported by NFS in the past,
> and expects to be exported by NFS in the future, reorg'ing a directory
> will seriously confuse any clients which have cached NFS handles.)
>
> For that reason, historically we've never bothered to try to implement
> ways of decreasing the size of a directory --- especially since in
> most cases, sysadmins can do something like:
>
> mkdir foo.new ; mv foo/* foo.new ; mv foo.new foo
>
> which while isn't perfect, works most of the time.
>
> Regards,
>
> - Ted
Thanks for your patient explanations, Eric & Ted!
Regards,
Wang Sheng-Hui
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-08-04 4:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 14:19 Use fsck to free the space used by dir? Wang Sheng-Hui
2012-08-03 15:18 ` Eric Sandeen
2012-08-03 17:57 ` Theodore Ts'o
2012-08-04 4:25 ` Wang Sheng-Hui [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=501CA44D.2010201@gmail.com \
--to=shhuiw@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).