From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>, linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] xfs: remove experimental tag for reflinks
Date: Wed, 22 Nov 2017 13:00:23 -0800 [thread overview]
Message-ID: <20171122210023.GJ2135@magnolia> (raw)
In-Reply-To: <CAOQ4uxjzpBrzMnt-OFP4P_6DB5onw9U+BM+4Dd_BpaeaPQ86iQ@mail.gmail.com>
On Wed, Nov 22, 2017 at 10:40:07PM +0200, Amir Goldstein wrote:
> On Wed, Nov 22, 2017 at 8:31 PM, Darrick J. Wong
> <darrick.wong@oracle.com> wrote:
> > On Wed, Nov 15, 2017 at 08:14:33AM +0200, Amir Goldstein wrote:
> [...]
> >>
> >> Last time you wrote about this bug you had a "hard question" about transaction
> >> reservation for the solution and said your're going to go have a think about it:
> >> https://marc.info/?l=linux-xfs&m=150766311924170&w=2
> >> Did you come to any conclusions?
> >> That sounds like one of those nasty CoW corner cases, so I'd be happy to know
> >> there is at least a well thought design for a solution - if not a fix.
> >
> > Sorry I let myself get distracted/stressed with the merge window;
> > hopefully the patch I sent out will address that problem?
> >
>
> Problem reproduces better on a spinning rust I have at the office, so will
> give it a spin tomorrow.
Ok.
> >> Practically, I would love if that bug could be solved soon so that we can all
> >> start running generic/503 for more than a few iterations to stress
> >> test reflink/cow
> >> with power failure. Success on this front could be a big upside before
> >> turning off
> >> EXPERIMENTAL.
> >
> > Indeed! What is the status of those tests, anyway? Are they in xfstests?
> >
>
> Yes.
Excellent!
> 2 fsx stress tests, with and without clones
> generic/455
> generic/457
> (replay group)
>
> One regression test for ext4 crash bug that was already fixed
> generic/456
>
> And one regression test for xfs reflink crash bug that you already fixed
> generic/458
>
> So generic/457 is the one we should be hammering (fsx and reflink)
Ok, will do.
--D
> it creates 10 clones and runs fsx workers on them.
> I imagine it is not long before there are no more shared extents.
> It's not much, but its a good start.
> I recon it would be good if you guys added some more variants of this test
> to try and cover more interesting reflink cases.
>
> FYI, Josef also has an fsstress based test, but it is plain shell script
> and I never got around to adapting it to an xfstest:
> https://github.com/josefbacik/log-writes
>
> Cheers,
> Amir.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-11-22 21:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 14:54 [PATCH] xfs: remove experimental tag for reflinks Christoph Hellwig
2017-08-31 6:40 ` Darrick J. Wong
2017-08-31 12:43 ` Brian Foster
2017-08-31 13:30 ` Christoph Hellwig
2017-08-31 15:31 ` Darrick J. Wong
2017-08-31 15:55 ` Eric Sandeen
2017-08-31 20:02 ` Darrick J. Wong
2017-08-31 15:59 ` Brian Foster
2017-08-31 20:09 ` Darrick J. Wong
2017-08-31 20:36 ` Brian Foster
2017-08-31 22:58 ` Dave Chinner
2017-09-01 11:16 ` Brian Foster
2017-08-31 22:19 ` Dave Chinner
2018-01-08 21:43 ` Darrick J. Wong
2018-01-08 22:11 ` Dave Chinner
2017-11-15 1:10 ` Darrick J. Wong
2017-11-15 6:14 ` Amir Goldstein
2017-11-22 18:31 ` Darrick J. Wong
2017-11-22 20:40 ` Amir Goldstein
2017-11-22 21:00 ` Darrick J. Wong [this message]
2017-11-23 10:44 ` Amir Goldstein
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=20171122210023.GJ2135@magnolia \
--to=darrick.wong@oracle.com \
--cc=amir73il@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.