public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH v2] xfs: use per-AG reservations for the finobt
Date: Tue, 24 Jan 2017 08:48:37 -0800	[thread overview]
Message-ID: <20170124164837.GI4780@birch.djwong.org> (raw)
In-Reply-To: <20170124140247.GA26149@lst.de>

On Tue, Jan 24, 2017 at 03:02:47PM +0100, Christoph Hellwig wrote:
> On Mon, Jan 23, 2017 at 11:28:47AM -0800, Darrick J. Wong wrote:
> > I also want to warn more loudly about AGs that don't actually have
> > enough space to handle the reservation.
> 
> > > +			xfs_warn(mp,
> > > +"Per-AG reservation for finobt failed.  File System may run out of space.\n");
> > > +			mp->m_inotbt_nores = true;
> > > +		}
> 
> Any suggestion for a better warning than this one?  Except for this
> bit I'm ready to resend the series.

I'd just print out:

"Per-AG reservation for AG ${agno} failed.  Filesystem may run out of space."

if any of the (now three) invocations of __xfs_ag_resv_init() returns
ENOSPC, since the AG is more than 98% full.  Some day, a sysadmin could
then use the fsmap data to identify which inodes are using the most
space in that AG and arrange to migrate/remove/etc the data to another
AG.

--D

  reply	other threads:[~2017-01-24 16:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-23 18:05 [PATCH v2] xfs: use per-AG reservations for the finobt Christoph Hellwig
2017-01-23 19:28 ` Darrick J. Wong
2017-01-24 14:02   ` Christoph Hellwig
2017-01-24 16:48     ` Darrick J. Wong [this message]
2017-01-24 19:50       ` Christoph Hellwig
2017-01-24 20:05         ` Darrick J. Wong
2017-01-24 14:06 ` Brian Foster
2017-01-24 14:49   ` Christoph Hellwig
2017-01-24 16:19     ` Brian Foster
2017-01-24 18:27       ` Darrick J. Wong

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=20170124164837.GI4780@birch.djwong.org \
    --to=darrick.wong@oracle.com \
    --cc=hch@lst.de \
    --cc=linux-xfs@vger.kernel.org \
    /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