linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] ext4: add max_dir_size_kb mount option
Date: Fri, 10 Aug 2012 14:38:10 -0500	[thread overview]
Message-ID: <50256322.9040409@redhat.com> (raw)
In-Reply-To: <1344626638-31548-1-git-send-email-tytso@mit.edu>

On 8/10/12 2:23 PM, Theodore Ts'o wrote:
> 
> So it is useful, in cloud server/data center environments, to be able
> to set a filesystem-wide cap on the maximum size of a directory, to
> ensure that directories never get larger than a sane size.  We do this
> via a new mount option, max_dir_size_kb.  If there is an attempt to
> grow the directory larger than max_dir_size_kb, the system call will
> return ENOSPC instead.

Can the commit message also describe more about the problem: how bad
it is, the root cause, and why it's so hard to fix properly?

Please also update Documentation/filesystems/ext4.txt so people
know for sure what the use & intent of this new knob is.

I guess it's self explanatory in the name but docs are easy & good.

-Eric

  reply	other threads:[~2012-08-10 19:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-10 19:23 [PATCH] ext4: add max_dir_size_kb mount option Theodore Ts'o
2012-08-10 19:38 ` Eric Sandeen [this message]
2012-08-10 19:59   ` Theodore Ts'o
2012-08-10 20:16     ` Eric Sandeen
2012-08-10 21:59       ` Theodore Ts'o
2012-08-10 20:11 ` Jeff Moyer
2012-08-10 21:58   ` Theodore Ts'o
2012-08-10 23:14     ` Andreas Dilger
2012-08-11  1:40     ` [PATCH -v2] " Theodore Ts'o
2012-08-11  3:22       ` Andreas Dilger
2012-08-11 19:26         ` Theodore Ts'o
2012-08-11 21:10           ` Andreas Dilger
2012-08-11 21:13           ` Ted Ts'o

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=50256322.9040409@redhat.com \
    --to=sandeen@redhat.com \
    --cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).