From: "Johnson Yan" <johnson_yan@usish.com>
To: 'Jack Wang' <jack.wang.usish@gmail.com>, 'NeilBrown' <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: RE: RAID0 DeviceDisappeared event happen when restart mdmonitor service
Date: Mon, 17 Sep 2012 11:23:40 +0800 [thread overview]
Message-ID: <016e01cd9483$d5690a70$803b1f50$@com> (raw)
In-Reply-To: <CA+res+RvgxtHmYHw3DMCm7La9AFoCzxM93YLKJYvYy7EwBYyfw@mail.gmail.com>
Hi Neil,
Thank you for the clarification.
I can remove the RAID0 MD's information from /etc/mdadm.conf to omit the monitor for RAID0, then so such event occurred when restart mdmonitor service, but the system won't re-assemble these RAID0 MD after every system reboot.
Do you have any good advice?
Best Regards,
Johnson
> Thanks Neil for always kindly help.
> The device disappeared event report when restart mdmonitor service, which
> will mdadm with options PIDFILE=/var/run/mdadm/mdadm.pid
> PATH=/sbin:/usr/sbin:$PATH
> RETVAL=0
> OPTIONS="-F -y -f -s -i $PIDFILE"
>
> And I checked man page of mdadm which clear claimed :
>
>
> DeviceDisappeared
> An md array which previously was configured
> appears to no
> longer be configured. (syslog priority: Critical)
>
> If mdadm was told to monitor an array which is RAID0 or
> Lin-
> ear, then it will report DeviceDisappeared with the
> extra
> information Wrong-Level. This is because RAID0 and
> Linear
> do not support the device-failed, hot-spare and resync
> oper-
> ations which are monitored.
>
> Thanks again for your time.
>
> Jack
next prev parent reply other threads:[~2012-09-17 3:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 10:02 RAID0 DeviceDisappeared event happen when restart mdmonitor service Johnson Yan
2012-09-17 2:30 ` Jack Wang
2012-09-17 2:44 ` Johnson Yan
2012-09-17 2:48 ` NeilBrown
2012-09-17 3:03 ` Jack Wang
2012-09-17 3:23 ` Johnson Yan [this message]
2012-10-24 2:10 ` NeilBrown
2012-10-24 4:29 ` Johnson Yan
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='016e01cd9483$d5690a70$803b1f50$@com' \
--to=johnson_yan@usish.com \
--cc=jack.wang.usish@gmail.com \
--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 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.