From: Christoph Hellwig <hch@infradead.org>
To: Chris Cottam <chris.cottam@bytemark.co.uk>
Cc: Christoph Hellwig <hch@infradead.org>, linux-xfs@vger.kernel.org
Subject: Re: XFS reflinks
Date: Tue, 29 Aug 2017 09:40:56 -0700 [thread overview]
Message-ID: <20170829164056.GA22055@infradead.org> (raw)
In-Reply-To: <d1c6f429-fc41-0e38-b704-444273aaae9e@bytemark.co.uk>
On Tue, Aug 29, 2017 at 02:39:56PM +0100, Chris Cottam wrote:
> Could I enquire about the severity of a few issues?
The most recent ones were:
xfs: try to avoid blowing out the transaction reservation when bunmaping a shared extent
which is a case wher we blew a transaction under extreme unlink
loads, leading to a fs shutdown in those cases.
xfs: try any AG when allocating the first btree block when reflinking
again could lead to a shutdown
xfs: fix COW writeback race
this could lead to a kernel crash
xfs: only reclaim unwritten COW extents periodically
could lead to a kernel crash
next prev parent reply other threads:[~2017-08-29 16:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 11:23 XFS reflinks Chris Cottam
2017-08-29 13:00 ` Christoph Hellwig
2017-08-29 13:39 ` Chris Cottam
2017-08-29 16:40 ` Christoph Hellwig [this message]
2017-08-29 16:03 ` Darrick J. Wong
2017-08-29 16:23 ` Christoph Hellwig
2017-08-29 22:03 ` Dave Chinner
2017-08-30 7:03 ` Christoph Hellwig
2017-08-31 10:33 ` Chris Cottam
2017-08-31 13:09 ` 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=20170829164056.GA22055@infradead.org \
--to=hch@infradead.org \
--cc=chris.cottam@bytemark.co.uk \
--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