From: Zorro Lang <zlang@redhat.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: linux-xfs@vger.kernel.org, fstests@vger.kernel.org,
tytso@mit.edu, leah.rumancik@gmail.com
Subject: Re: [PATCH 1/2] common/rc: wait for udev before creating dm targets
Date: Fri, 29 Jul 2022 01:52:38 +0800 [thread overview]
Message-ID: <20220728175238.irv435n46bfet64b@zlang-mailbox> (raw)
In-Reply-To: <165886491692.1585061.2529733779998396096.stgit@magnolia>
On Tue, Jul 26, 2022 at 12:48:36PM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <djwong@kernel.org>
>
> Every now and then I see a failure when running generic/322 on btrfs:
>
> QA output created by 322
> failed to create flakey device
>
> Looking in the 322.full file, I see:
>
> device-mapper: reload ioctl on flakey-test (253:0) failed: Device or resource busy
> Command failed.
>
> And looking in dmesg, I see:
>
> device-mapper: table: 8:3: linear: Device lookup failed (-16)
> device-mapper: ioctl: error adding target to table
>
> /dev/block/8:3 corresponds to the SCRATCH_DEV on this system. Given the
> failures in 322.out, I think this is caused by generic/322 calling
> _init_flakey -> _dmsetup_create -> $DMSETUP_PROG create being unable to
> open SCRATCH_DEV exclusively. Add a call to $UDEV_SETTLE_PROG prior to
> the creation of the target to try to calm the system down sufficiently
> that the test can proceed.
>
> Note that I don't have any hard evidence that it's udev at fault here --
> the few times I've caught this thing, udev *has* been active spraying
> error messages for nonexistent sysfs paths to journald and adding a
> 'udevadm settle' seems to fix it... but that's still only
> circumstantial. Regardless, it seems to have fixed the test failure.
>
> Signed-off-by: Darrick J. Wong <djwong@kernel.org>
> ---
> common/rc | 5 +++++
> 1 file changed, 5 insertions(+)
>
>
> diff --git a/common/rc b/common/rc
> index f4469464..60a9bacd 100644
> --- a/common/rc
> +++ b/common/rc
> @@ -4815,6 +4815,11 @@ _dmsetup_remove()
>
> _dmsetup_create()
> {
> + # Wait for udev to settle so that the dm creation doesn't fail because
> + # some udev subprogram opened one of the block devices mentioned in the
> + # table string w/ O_EXCL. Do it again at the end so that an immediate
> + # device open won't also fail.
> + $UDEV_SETTLE_PROG >/dev/null 2>&1
No objection from me, as you've proved it works for your issue:)
Reviewed-by: Zorro Lang <zlang@redhat.com>
> $DMSETUP_PROG create "$@" >>$seqres.full 2>&1 || return 1
> $DMSETUP_PROG mknodes >/dev/null 2>&1
> $UDEV_SETTLE_PROG >/dev/null 2>&1
>
next prev parent reply other threads:[~2022-07-28 17:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 19:48 [PATCHSET 0/2] dmerror: support external log and rt devices Darrick J. Wong
2022-07-26 19:48 ` [PATCH 1/2] common/rc: wait for udev before creating dm targets Darrick J. Wong
2022-07-28 17:52 ` Zorro Lang [this message]
2022-07-28 18:41 ` Christoph Hellwig
2022-08-08 5:32 ` Naohiro Aota
2022-07-26 19:48 ` [PATCH 2/2] dmerror: support external log and realtime devices Darrick J. Wong
2022-07-28 18:16 ` Zorro Lang
2022-07-30 10:18 ` Zorro Lang
2022-07-31 16:48 ` Darrick J. Wong
2022-07-31 18:10 ` Zorro Lang
2022-08-01 14:46 ` Zorro Lang
2022-08-01 21:10 ` Darrick J. Wong
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=20220728175238.irv435n46bfet64b@zlang-mailbox \
--to=zlang@redhat.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=leah.rumancik@gmail.com \
--cc=linux-xfs@vger.kernel.org \
--cc=tytso@mit.edu \
/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