linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: tytso@mit.edu
Cc: linux-ext4@vger.kernel.org, Andreas Dilger <adilger@dilger.ca>
Subject: Reserved inodes
Date: Mon, 14 Dec 2015 11:50:40 +0100	[thread overview]
Message-ID: <20151214105040.GE8474@quack.suse.cz> (raw)

Hello Ted,

could you please decide which way do we solve the problem of running out of
reserved inodes? Whether we raise the number of reserved inodes in the
superblock or whether we go down via the path of dedicated system
directory. I somewhat prefer the first solution and have submitted patches
[1] which enable (IMHO rather smooth) move in that direction. If you decide
for the second solution, so be it, I will support it anyway but we need a
final word to be said. Current situation only complicates the situation
with project quota patches and my orphan scalability series is blocked by
that as well for several months already...

								Honza

[1] http://lists.openwall.net/linux-ext4/2015/08/26/27

-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

                 reply	other threads:[~2015-12-14 10:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20151214105040.GE8474@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=adilger@dilger.ca \
    --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).