FS/XFS testing framework
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: zlang@kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH] xfs/541: _notrun if the file system can't mount
Date: Wed, 29 Jan 2025 13:06:24 -0800	[thread overview]
Message-ID: <20250129210624.GZ3557695@frogsfrogsfrogs> (raw)
In-Reply-To: <20250129054918.GA29053@lst.de>

On Wed, Jan 29, 2025 at 06:49:18AM +0100, Christoph Hellwig wrote:
> On Tue, Jan 28, 2025 at 11:25:06AM -0800, Darrick J. Wong wrote:
> > On Tue, Jan 28, 2025 at 08:14:48AM +0100, Christoph Hellwig wrote:
> > > A file system created without an RT section might not be able to mount
> > > with an rtdev specified if the RT device has a larger LBA size.
> > 
> > Where does the mount failure occur?  The initial mount (where we specify
> > -o rtdev but sb_rblocks is still zero) should succeed because
> > xfs_rtmount_init ignores m_rtdev_targp if !rblocks, right?  So it's only
> > when you get to growfs and we try to read the device that things fail?
> 
> There only is a single mount in the test.
> 
> The test only clears the rtdev for the mkfs call, not the mount call.
> As XFS doesn't allow adding a new rtdev at runtime, just expanding the
> file system to the already passed but not actually used rt device in
> growfs that's actually needed, even if it sounds counterintuitive.
> 
> (that being said I sent the patch directly from my zoned branch,
> so it won't apply as-is due to context issues)

Gross, it's the set_blocksize call in xfs_setsize_buftarg that trips
everything up.  But, it makes sense that one cannot mix sector sizes nor
mount an rtdev with a larger sector size than what's configured on the
data device.

Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>

--D

      reply	other threads:[~2025-01-29 21:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-28  7:14 [PATCH] xfs/541: _notrun if the file system can't mount Christoph Hellwig
2025-01-28 19:25 ` Darrick J. Wong
2025-01-29  5:49   ` Christoph Hellwig
2025-01-29 21:06     ` 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=20250129210624.GZ3557695@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=hch@lst.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox