From: NeilBrown <neilb@suse.de>
To: Hans-Peter Jansen <hpj@urpla.net>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Persistent failures with simple md setup
Date: Wed, 13 Mar 2013 11:52:35 +1100 [thread overview]
Message-ID: <20130313115235.01492c21@notabene.brown> (raw)
In-Reply-To: <4291349.FrQcKOnicQ@xrated>
[-- Attachment #1: Type: text/plain, Size: 733 bytes --]
hi,
wonder if you could try one more test for me.
With the other (echo BEFORE / echo AFTER etc) tracing still there, change the
/sbin/udevadm settle --timeout=$MDADM_DEVICE_TIMEOUT
to
/sbin/udevadm --debug settle --timeout=$MDADM_DEVICE_TIMEOUT > /dev/kmsg 2>&1
I found there is a case where "udevadm settle" can exit before the queue is
empty. It seems like a very unlikely scenario, but it seems clear that
something "unlikely" is happening.
I'm hoping to see
timeout waiting for udev queue
appear in the logs when this runs.
If you could add that and post the 'dmesg' output if you ever get that
message - or maybe even if you don't - that would be very helpful.
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-03-13 0:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 22:14 Persistent failures with simple md setup Hans-Peter Jansen
2013-01-30 9:07 ` Sebastian Riemer
2013-01-30 17:12 ` Hans-Peter Jansen
2013-02-04 20:43 ` Hans-Peter Jansen
2013-02-05 3:44 ` NeilBrown
2013-02-27 17:01 ` Hans-Peter Jansen
2013-02-28 3:40 ` NeilBrown
2013-02-28 10:49 ` Hans-Peter Jansen
2013-02-28 21:25 ` NeilBrown
2013-02-28 22:16 ` Hans-Peter Jansen
[not found] ` <4291349.FrQcKOnicQ@xrated>
2013-03-03 23:33 ` NeilBrown
2013-03-13 0:52 ` NeilBrown [this message]
2013-03-15 22:43 ` Hans-Peter Jansen
2013-03-18 11:20 ` Hans-Peter Jansen
2013-03-21 3:24 ` NeilBrown
2013-04-10 13:28 ` Hans-Peter Jansen
2013-04-10 13:44 ` Hans-Peter Jansen
2013-04-11 7:33 ` NeilBrown
2013-01-30 9:20 ` Roy Sigurd Karlsbakk
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=20130313115235.01492c21@notabene.brown \
--to=neilb@suse.de \
--cc=hpj@urpla.net \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).