From: Eric Sandeen <sandeen@sandeen.net>
To: Alexander Tsvetkov <alexander.tsvetkov@oracle.com>,
Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: maxpct option for small xfs filesystems
Date: Wed, 28 Jan 2015 12:05:27 -0600 [thread overview]
Message-ID: <54C924E7.5020404@sandeen.net> (raw)
In-Reply-To: <54C8BCEC.5050101@oracle.com>
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.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev 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:
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=54C924E7.5020404@sandeen.net \
--to=sandeen@sandeen.net \
--cc=alexander.tsvetkov@oracle.com \
--cc=david@fromorbit.com \
--cc=xfs@oss.sgi.com \
/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