From: Christoph Hellwig <hch@infradead.org>
To: Chris Cottam <chris.cottam@bytemark.co.uk>
Cc: linux-xfs@vger.kernel.org
Subject: Re: XFS reflinks
Date: Tue, 29 Aug 2017 06:00:46 -0700 [thread overview]
Message-ID: <20170829130046.GA28896@infradead.org> (raw)
In-Reply-To: <04eacb90-aac9-7c47-f074-fa91eb253822@bytemark.co.uk>
On Tue, Aug 29, 2017 at 12:23:13PM +0100, Chris Cottam wrote:
> I've got a project where being able to take COW copies of a VMs disc
> would be really useful (disc snapshots to be then archived off elsewhere)
>
> How stable is the the experimental reflinks feature and do you have any
> idea when it might be declared stable?
I've got a customer that heavily uses (and tests) reflinks. They
initially found a few issues, but these days the QA teams finds
bugs in decade old XFS code but not related to reflinks..
You're mileage my vary, but I think we should be able to drop the
experimental tag now.
next prev parent reply other threads:[~2017-08-29 13:00 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 [this message]
2017-08-29 13:39 ` Chris Cottam
2017-08-29 16:40 ` Christoph Hellwig
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=20170829130046.GA28896@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