From: Eryu Guan <eguan@redhat.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: fstests <fstests@vger.kernel.org>
Subject: Re: [PATCH] xfstests: test orphan inode recovery on RO mount
Date: Sat, 11 Mar 2017 19:28:52 +0800 [thread overview]
Message-ID: <20170311112852.GS14226@eguan.usersys.redhat.com> (raw)
In-Reply-To: <e3f1b026-16e7-38e5-5af3-4e475caa94d8@redhat.com>
On Fri, Mar 10, 2017 at 08:20:36AM -0600, Eric Sandeen wrote:
> On 3/9/17 10:36 PM, Eryu Guan wrote:
> > On Thu, Mar 09, 2017 at 03:31:43PM -0600, Eric Sandeen wrote:
> >> There's a bug in xfs where the orphan inode list
> >> is not processed on a readonly mount, and is still not
> >> processed even if it gets mounted rw. This test exercises
> >> that, and makes sure that the unlinked list is empty after
> >> a transition to rw and an unmount.
> >>
> >> While we're at it, sanity check the same thing for pure ro
> >> and rw unmounts.
> >>
> >> Now that shutdown is generic, we can test other filesystems
> >> as well, so this is in the generic group.
> >>
> >> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
>
> ...
>
> > Do we really need 10s? That seems a bit long to me, and I tested with
> > sleep 3, it also reproduced on XFS (4.11-rc1).
> >
> > Otherwise look good to me. I can fix them all at commit time if you're
> > OK with "sleep 3".
>
> Sure, thanks. The 10s came from another test w/ the same setup.
> Happy to resend too, if you'd prefer.
No worries, I've fixed them up and gone through release testing.
Thanks,
Eryu
prev parent reply other threads:[~2017-03-11 11:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 21:31 [PATCH] xfstests: test orphan inode recovery on RO mount Eric Sandeen
2017-03-10 4:36 ` Eryu Guan
2017-03-10 14:20 ` Eric Sandeen
2017-03-11 11:28 ` Eryu Guan [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=20170311112852.GS14226@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=sandeen@redhat.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