From: Hans-Peter Jansen <hpj@urpla.net>
To: NeilBrown <neilb@suse.de>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Persistent failures with simple md setup
Date: Wed, 10 Apr 2013 15:44:25 +0200 [thread overview]
Message-ID: <113804746.rOsYdmQaaH@xrated> (raw)
In-Reply-To: <20130321142459.2cd6b4da@notabene.brown>
[-- Attachment #1: Type: text/plain, Size: 683 bytes --]
On Donnerstag, 21. März 2013 14:24:59 NeilBrown wrote:
>
> Thanks! Unfortunately it is not as helpful as I hoped, but it does suggest
> that "udevadm settle" does sometimes appear to misbehave even if there
> aren't any problems with the md array.
>
> Could I ask for one more?
> Prefix the "udevadm settle " command with
> strace -o /tmp/udevadm.trace -s 500
>
> (making sure that you have 'strace' installed) and then post the
> "/tmp/udevadm.trace" file. Hopefully that will at least allow me to rule
> out some possibilities.
After reducing the timeout to 40 secs, we're able to catch a failure today
with two degraded arrays: md0 and md1.
Cheers,
Pete
[-- Attachment #2: udevadm.trace.gz --]
[-- Type: application/x-gzip, Size: 5524 bytes --]
next prev parent reply other threads:[~2013-04-10 13:44 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
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 [this message]
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=113804746.rOsYdmQaaH@xrated \
--to=hpj@urpla.net \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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