From: Vivek Goyal <vgoyal@redhat.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: overlayfs <linux-unionfs@vger.kernel.org>,
Miklos Szeredi <miklos@szeredi.hu>,
David Howells <dhowells@redhat.com>,
fstests <fstests@vger.kernel.org>,
Chandan Rajendra <chandan@linux.vnet.ibm.com>
Subject: Re: [ANNOUNCE] unionmount-testsuite: Amir's master branch updated
Date: Mon, 11 Dec 2017 15:59:12 -0500 [thread overview]
Message-ID: <20171211205912.GD13399@redhat.com> (raw)
In-Reply-To: <CAOQ4uxhb4yVTt29E0XFYY_OT_ubQ5w0Zgqojn=y7nH+XSZ90GA@mail.gmail.com>
On Mon, Dec 11, 2017 at 10:47:15PM +0200, Amir Goldstein wrote:
[..]
> > - For the xfs reflink test, I am curious that why have you recommended
> > to also enabled "rmapbt=1". Is is required for the tests?
> >
>
> You cannot enable reflink=1 without it.
I could do that. Here is the xfs_info output which shows rmapbt=0 and
reflink=1.
# xfs_info /mnt/test-xfs
meta-data=/dev/mapper/test--union-lower_layer isize=512 agcount=4, agsize=327680 blks
= sectsz=512 attr=2, projid32bit=1
= crc=1 finobt=1 spinodes=0 rmapbt=0
= reflink=1
data = bsize=4096 blocks=1310720, imaxpct=25
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0 ftype=1
log =internal bsize=4096 blocks=2560, version=2
= sectsz=512 sunit=0 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
Vivek
next prev parent reply other threads:[~2017-12-11 20:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 20:20 [ANNOUNCE] unionmount-testsuite: Amir's master branch updated Amir Goldstein
2017-12-06 9:09 ` Miklos Szeredi
2017-12-06 18:17 ` Vivek Goyal
2017-12-06 19:14 ` Amir Goldstein
2017-12-08 16:29 ` Amir Goldstein
2017-12-11 19:59 ` Vivek Goyal
2017-12-11 20:47 ` Amir Goldstein
2017-12-11 20:59 ` Vivek Goyal [this message]
2017-12-12 0:10 ` Dave Chinner
2017-12-12 6:02 ` Amir Goldstein
2017-12-12 14:53 ` Christoph Hellwig
2017-12-12 15:00 ` 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=20171211205912.GD13399@redhat.com \
--to=vgoyal@redhat.com \
--cc=amir73il@gmail.com \
--cc=chandan@linux.vnet.ibm.com \
--cc=dhowells@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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