From: Nathan Scott <nscott@aconex.com>
To: David Chinner <dgc@sgi.com>
Cc: Timothy Shimmin <tes@sgi.com>, xfs-dev <xfs-dev@sgi.com>,
xfs-oss <xfs@oss.sgi.com>
Subject: Re: Review: Be smarter about handling ENOSPC during writeback
Date: Tue, 12 Jun 2007 09:13:45 +1000 [thread overview]
Message-ID: <1181603625.3758.53.camel@edge.yarra.acx> (raw)
In-Reply-To: <20070608073342.GW85884050@sgi.com>
On Fri, 2007-06-08 at 17:33 +1000, David Chinner wrote:
> On Fri, Jun 08, 2007 at 03:28:14PM +1000, Timothy Shimmin wrote:
> > Will we get questions from people about reduced space from df? :)
>
> If we do, I think you just volunteered to write the FAQ entry ;)
It would be more correct of XFS to start doing the right thing by
reporting different values for b_free and b_avail in statfs(2) -
this code in xfs_mount.c::xfs_statvfs() ...
statp->f_bfree = statp->f_bavail =
sbp->sb_fdblocks - XFS_ALLOC_SET_ASIDE(mp);
I know this wasn't done for the original per-mount space reserving
ioctls (that was for one user though - dmapi, so I can see why there
may have been a shortcut done there) ... but if it affects everyone
now, there will be questions asked, and there is a standard interface
for reporting this space discrepency that tools like df(1) already
use.
cheers.
next prev parent reply other threads:[~2007-06-11 23:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 4:52 Review: Be smarter about handling ENOSPC during writeback David Chinner
2007-06-04 6:13 ` Timothy Shimmin
2007-06-08 5:28 ` Timothy Shimmin
2007-06-08 7:33 ` David Chinner
2007-06-11 23:13 ` Nathan Scott [this message]
2007-06-12 3:09 ` David Chinner
2007-06-04 9:41 ` Timothy Shimmin
2007-06-04 14:11 ` David Chinner
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=1181603625.3758.53.camel@edge.yarra.acx \
--to=nscott@aconex.com \
--cc=dgc@sgi.com \
--cc=tes@sgi.com \
--cc=xfs-dev@sgi.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