All of
 help / color / mirror / Atom feed
From: Eric Sandeen <>
To: Alexander Tsvetkov <>,
	Dave Chinner <>
Subject: Re: maxpct option for small xfs filesystems
Date: Wed, 28 Jan 2015 12:05:27 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 1/28/15 4:41 AM, Alexander Tsvetkov wrote:
> What is expected behaviour in this case when it's required for fs to allocate new inodes starting to exceed defined maxpct
> percentage? Which error is expected to be returned to user, enospc or probably just some warning?

Sorry, I didn't answer this.  ENOSPC is expected.

There's not a lot of value in enforcing this strictly to the last inode,
because a % is fairly coarse anyway, but we should not blow right past
it as we do today.


xfs mailing list

      parent reply	other threads:[~2015-01-28 18:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-26 16:14 maxpct option for small xfs filesystems Alexander Tsvetkov
2015-01-26 22:37 ` Dave Chinner
2015-01-27 16:23   ` Alexander Tsvetkov
2015-01-27 16:31     ` Eric Sandeen
2015-01-27 19:15       ` Eric Sandeen
2015-01-28 10:41       ` Alexander Tsvetkov
2015-01-28 15:44         ` Eric Sandeen
2015-01-28 18:05         ` Eric Sandeen [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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.