From: "Darrick J. Wong" <djwong@kernel.org>
To: Hans Holmberg <Hans.Holmberg@wdc.com>
Cc: "fstests@vger.kernel.org" <fstests@vger.kernel.org>,
"zlang@kernel.org" <zlang@kernel.org>,
"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
Carlos Maiolino <cem@kernel.org>,
"david@fromorbit.com" <david@fromorbit.com>, hch <hch@lst.de>
Subject: Re: [PATCH 2/2] xfs: add mount test for read only log devices
Date: Mon, 28 Apr 2025 08:58:42 -0700 [thread overview]
Message-ID: <20250428155842.GR25675@frogsfrogsfrogs> (raw)
In-Reply-To: <1c313919-f6ca-4f53-be69-21fe93e97b0e@wdc.com>
On Mon, Apr 28, 2025 at 12:16:34PM +0000, Hans Holmberg wrote:
> On 25/04/2025 17:05, Darrick J. Wong wrote:
> > ps this test should check
> > that a readonly log device results in a norecovery mount and that
> > pending changes don't show up if the mount succeeds?
> >
> > Also, ext4 supports external log devices, should this be in
> > tests/generic?
>
> Doh!, actually ext4 has a test for this already, ext4/002
> (also based on generic/050)
>
> With my fix, ext4/002 passes for xfs Should/can we turn that into a
> generic test?
Yeah, it looks like ext4/002 already does most of what you want. Though
I'd amend it to check that SCRATCH_MNT/00-99 aren't visible in the
norecovery mounts and only appear after recovery actually runs.
> The test makes sure that a filesystem will mount ro,norecovery if
> the log device is ro but does not do any real checks if recovery is
> prevented (or done once the log device is rw again).
> That could be added though.
<nod>
--D
next prev parent reply other threads:[~2025-04-28 15:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 9:03 [PATCH 0/2] add read-only logdev/rtdev mount-remount tests Hans Holmberg
2025-04-25 9:03 ` [PATCH 1/2] xfs: add mount test for read only rt devices Hans Holmberg
2025-04-25 15:03 ` Darrick J. Wong
2025-04-29 12:03 ` Hans Holmberg
2025-04-29 14:52 ` Darrick J. Wong
2025-04-30 12:56 ` hch
2025-04-30 14:49 ` Darrick J. Wong
2025-05-07 8:57 ` Hans Holmberg
2025-05-07 10:23 ` Hans Holmberg
2025-04-25 9:03 ` [PATCH 2/2] xfs: add mount test for read only log devices Hans Holmberg
2025-04-25 15:05 ` Darrick J. Wong
2025-04-28 12:16 ` Hans Holmberg
2025-04-28 15:58 ` Darrick J. Wong [this message]
2025-04-30 8:26 ` Hans Holmberg
2025-04-30 14:52 ` Darrick J. Wong
2025-05-02 11:40 ` Hans Holmberg
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=20250428155842.GR25675@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=Hans.Holmberg@wdc.com \
--cc=cem@kernel.org \
--cc=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=hch@lst.de \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@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.