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 14:59:20 -0500 [thread overview]
Message-ID: <20171211195920.GA13399@redhat.com> (raw)
In-Reply-To: <CAOQ4uxjM6ZLcyU5-nQXz=T98kuhMrCJ+1df85-19QJQjrr7JiA@mail.gmail.com>
On Fri, Dec 08, 2017 at 06:29:53PM +0200, Amir Goldstein wrote:
> On Wed, Dec 6, 2017 at 9:14 PM, Amir Goldstein <amir73il@gmail.com> wrote:
> > On Wed, Dec 6, 2017 at 8:17 PM, Vivek Goyal <vgoyal@redhat.com> wrote:
> >> On Tue, Dec 05, 2017 at 10:20:25PM +0200, Amir Goldstein wrote:
> >>> Hi All,
> >>>
> >>> The master branch on my unionmount-testsuite tree [1] has been updated.
> >>>
> >>> The head of the master branch is commit:
> >>> 6d04664 Add a test for rename over empty union dir
> >>>
> >>> This small update contains:
> >>> - A few new simple dir rename and dir remove tests
> >>> - A fix for running on kernel <= v4.9 with no redirect_dir support
> >>> - A new setup option --squashfs to setup lower as read-only squashfs
> >>>
> >>
> >> Hi Amir,
> >>
> >> It would be nice to also update README file and explain different options.
> >
> > Yes, that would be nice... will get to it some day if someone doesn't
> > beat me to it.
> >
> >>
> >> Also, how to test with different mount options enabled/disable (index,
> >> redirect etc).
> >>
> >
> > A preview for README:
> > Basically, the testsuite tests for correctness, so if correctness requires
> > enabling a feature, then testsuite will fail without the feature, but there are
> > some historical exceptions:
> > - testsuite predates redirect_dir, so I let the testsuite auto detect
> > redirect_dir
> > and kept the "expect EXDEV" logic for redirect_dir disabled
> > - until quite recently st_ino was not constant on copy up in most cases,
> > so the verification of constant ino was added as an opt-in feature
> > with --verify
> >
> >
> >>> With index enabled, there are no known failures.
> >>> With index disabled this test fails on non-constant st_ino for lower hardlink
> >>> copy up:
> >>> run --ov=1 --samefs --verify rename-mass-5
> >
> > Thus, this test fails because with index disabled, hardlink is broken on copy up
> > and does not preserve st_ino.
> >
>
> Vivek,
>
> I added documentation about all the features I added to unionmount-testsuite at:
> https://github.com/amir73il/overlayfs/wiki/Overlayfs-testing#Unionmount_testsuite
>
> Will add that link to README on the next master branch update.
> Let me know if there is anything missing for you in this wiki page.
Hi Amir,
Thanks a lot for this documentation. I tested it and it works for me. So
far I was only running "./run --ov". Now I can do samefs setups and also
verify index feature etc.
Two minor nits/queries.
- Right now "./run --ov --samefs -s" fails if "/base" directory is not
there. So in mkdir command, add "base" to the list also.
- For the xfs reflink test, I am curious that why have you recommended
to also enabled "rmapbt=1". Is is required for the tests?
Thanks
Vivek
next prev parent reply other threads:[~2017-12-11 19: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 [this message]
2017-12-11 20:47 ` Amir Goldstein
2017-12-11 20:59 ` Vivek Goyal
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=20171211195920.GA13399@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 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.