From: "Daniel L. Miller" <dmiller@amfes.com>
To: linux-raid@vger.kernel.org
Subject: Re: Raid-10 mount at startup always has problem
Date: Thu, 25 Oct 2007 06:13:07 -0700 [thread overview]
Message-ID: <47209663.5000202@amfes.com> (raw)
In-Reply-To: <18208.13247.106651.142652@notabene.brown>
Neil Brown wrote:
> It might be worth finding out where mdadm is being run in the init
> scripts and add a "-v" flag, and redirecting stdout/stderr to some log
> file.
> e.g.
> mdadm -As -v > /var/log/mdadm-$$ 2>&1
>
> And see if that leaves something useful in the log file.
>
>
I haven't rebooted yet, but here's my /etc/udev/rules.d/70-mdadm.rules
file (BTW - running on Ubuntu 7.10 Gutsy):
SUBSYSTEM=="block", ACTION=="add|change",
ENV{ID_FS_TYPE}=="linux_raid*", RUN+="watershed -i udev-mdadm
/sbin/mdadm -As -v > /var/log/mdadm-$$ 2>&1"
# This next line (only) is put into the initramfs,
# where we run a strange script to activate only some of the arrays
# as configured, instead of mdadm -As:
#initramfs# SUBSYSTEM=="block", ACTION=="add|change",
ENV{ID_FS_TYPE}=="linux_raid*", RUN+="watershed -i udev-mdadm
/scripts/local-top/mdadm from-udev"
Could that initramfs line be causing the problem?
--
Daniel
next prev parent reply other threads:[~2007-10-25 13:13 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 18:14 Raid-10 mount at startup always has problem Daniel L. Miller
[not found] ` <46D49F1A.7030409@tmr.com>
2007-09-10 1:53 ` Daniel L. Miller
2007-09-10 2:04 ` Richard Scobie
[not found] ` <46E4A5F0.9090407@sauce.co.nz>
2007-09-10 2:11 ` Daniel L. Miller
2007-10-24 14:22 ` Daniel L. Miller
2007-10-24 16:25 ` Doug Ledford
2007-10-24 20:01 ` Bill Davidsen
2007-10-25 5:43 ` Daniel L. Miller
2007-10-25 6:40 ` Doug Ledford
2007-10-26 9:15 ` Luca Berra
2007-10-26 16:53 ` Gabor Gombas
2007-10-27 7:57 ` Luca Berra
2007-10-26 19:26 ` Doug Ledford
2007-10-27 7:50 ` Luca Berra
2007-10-27 15:07 ` Gabor Gombas
2007-10-27 20:47 ` Doug Ledford
2007-10-28 13:37 ` Luca Berra
2007-10-28 17:55 ` Doug Ledford
2007-10-29 0:21 ` Bill Davidsen
2007-10-29 7:41 ` Luca Berra
2007-10-29 13:22 ` Bill Davidsen
2007-10-29 15:21 ` Doug Ledford
2007-10-29 15:54 ` Gabor Gombas
2007-10-29 14:31 ` Doug Ledford
2007-10-29 5:59 ` Daniel L. Miller
2007-10-29 8:18 ` Luca Berra
2007-10-29 15:47 ` Doug Ledford
2007-10-29 21:29 ` Luca Berra
2007-10-29 23:15 ` Doug Ledford
2007-10-30 0:03 ` Daniel L. Miller
2007-11-01 13:56 ` Bill Davidsen
2007-12-17 14:58 ` Daniel L. Miller
2007-10-29 17:08 ` Doug Ledford
2007-10-29 18:56 ` Richard Scobie
2007-10-25 6:12 ` Neil Brown
2007-10-25 6:51 ` Doug Ledford
2007-10-25 13:13 ` Daniel L. Miller [this message]
2007-10-25 13:33 ` Daniel L. Miller
2007-10-26 6:12 ` Neil Brown
2007-10-25 14:46 ` Bill Davidsen
2007-10-25 16:13 ` Daniel L. Miller
2007-10-26 5:59 ` Neil Brown
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=47209663.5000202@amfes.com \
--to=dmiller@amfes.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.