From: Christoph Hellwig <hch@lst.de>
To: darrick.wong@oracle.com
Cc: bfoster@redhat.com, linux-xfs@vger.kernel.org
Subject: avoid running out of space during finobt insertation
Date: Tue, 24 Jan 2017 21:16:18 +0100 [thread overview]
Message-ID: <1485288980-17075-1-git-send-email-hch@lst.de> (raw)
Now growing into a series..
Changes since V2:
- improve error handling in __xfs_ag_resv_init
- improve mount time warning
Changes since V1:
- reduce the size of the reservation
- warn and fall back to the old somewhat buggy code if we can't
get the reservation at mount time
- read the AGF before asserting based on values in it
next reply other threads:[~2017-01-24 20:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 20:16 Christoph Hellwig [this message]
2017-01-24 20:16 ` [PATCH 1/2] xfs: only update mount/resv fields on success in __xfs_ag_resv_init Christoph Hellwig
2017-01-24 20:33 ` Darrick J. Wong
2017-01-24 20:16 ` [PATCH 2/2] xfs: use per-AG reservations for the finobt Christoph Hellwig
2017-01-24 20:42 ` Darrick J. Wong
2017-01-25 9:13 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2017-01-25 9:14 avoid running out of space during finobt insertation Christoph Hellwig
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=1485288980-17075-1-git-send-email-hch@lst.de \
--to=hch@lst.de \
--cc=bfoster@redhat.com \
--cc=darrick.wong@oracle.com \
--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;
as well as URLs for NNTP newsgroup(s).