From: Karel Zak <kzak@redhat.com>
To: Ruediger Meier <sweet_f_a@gmx.de>
Cc: util-linux@vger.kernel.org
Subject: Re: debug parallel root checks
Date: Fri, 9 Mar 2018 22:46:22 +0100 [thread overview]
Message-ID: <20180309214622.fys7a24fkiiyvrxa@ws.net.home> (raw)
In-Reply-To: <201803091606.08473.sweet_f_a@gmx.de>
On Fri, Mar 09, 2018 at 04:06:08PM +0100, Ruediger Meier wrote:
> On Friday 09 March 2018, Ruediger Meier wrote:
> > Hi,
> >
> > Our parallel root checks look already nice on the first view.
> > On the second view they fail the stress test, at least on my
> > system.
>
> Just an arbitrary example. Sometimes I get this failure
>
> $ cat tests/diff/mount/uuid
> --- /tmp/ul2/tests/expected/mount/uuid 2018-03-09 11:04:54.992654305 +0100
> +++ /tmp/ul2/tests/output/mount/uuid 2018-03-09 15:55:00.168028810 +0100
> @@ -1 +1,2 @@
> -Success
> +mount: /tmp/ul2/tests/output/mount/uuid-mnt: can't find UUID="f102445a-f6f3-4657-bc58-81ff164fc0d9".
> +A) Cannot find /dev/loop10 in /proc/mounts
>
>
> So mount can't find that UUID although it was found before by
> ts_uuid_by_devname, i.e. by blkid(1).
>
> What could be the problem:
> - another test thread removed the UUID
> - invalid blkid cache
> - a bug?
We do not use blkid cache, it should be based on udev symmlinks. The
symlinks are not ready yet. I guess sleep() or so fixed the problem.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2018-03-09 21:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 14:47 debug parallel root checks Ruediger Meier
2018-03-09 15:06 ` Ruediger Meier
2018-03-09 21:46 ` Karel Zak [this message]
2018-03-09 22:16 ` Ruediger Meier
2018-03-09 21:48 ` Karel Zak
2018-03-09 22:28 ` Ruediger Meier
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=20180309214622.fys7a24fkiiyvrxa@ws.net.home \
--to=kzak@redhat.com \
--cc=sweet_f_a@gmx.de \
--cc=util-linux@vger.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