From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Christoph Hellwig <hch@lst.de>
Cc: xfs@oss.sgi.com
Subject: Re: a couple xfstests fixes for reflinks
Date: Thu, 28 Jan 2016 13:02:55 -0800 [thread overview]
Message-ID: <20160128210255.GA6431@birch.djwong.org> (raw)
In-Reply-To: <1454001236-2600-1-git-send-email-hch@lst.de>
On Thu, Jan 28, 2016 at 06:13:52PM +0100, Christoph Hellwig wrote:
> See http://www.infradead.org/rpr.html
Hrmm, have I been sending junk again? I've noticed a few transient problems
with Oracle's mailservers lately...
> The patches (against Darrick's for-dave branch) fix various failures I see
> during testing XFS and NFS.
I've integrated your fixes with my dev tree and pushed to github.
There's a bunch of new tests in there to look at quota behaviors. Evidently
btrfs doesn't support classic usr/group quotas(?) and ocfs2 exploded when I
tried it, so for now I'll just charge each quota at reflink time; copy on write
is therefore "free".
--D
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2016-01-28 21:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 17:13 a couple xfstests fixes for reflinks Christoph Hellwig
2016-01-28 17:13 ` [PATCH 1/4] xfstests: fix scratch device filtering in 139 Christoph Hellwig
2016-01-28 19:24 ` Darrick J. Wong
2016-01-28 19:35 ` Darrick J. Wong
2016-01-28 17:13 ` [PATCH 2/4] xfstests: require dedup ioctl support in 182 Christoph Hellwig
2016-01-28 19:27 ` Darrick J. Wong
2016-01-28 17:13 ` [PATCH 3/4] xfstests: also treat EINVAL as reflink/dedup not supported Christoph Hellwig
2016-01-28 19:30 ` Darrick J. Wong
2016-01-28 17:13 ` [PATCH 4/4] xfstests: change to relative margins for reflinks tests Christoph Hellwig
2016-01-28 21:02 ` Darrick J. Wong [this message]
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=20160128210255.GA6431@birch.djwong.org \
--to=darrick.wong@oracle.com \
--cc=hch@lst.de \
--cc=xfs@oss.sgi.com \
/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