From: "Sergiusz Brzeziński" <Sergiusz.Brzezinski@supersystem.pl>
To: linux-raid@vger.kernel.org
Subject: mdadm --monitor: need extra feature?
Date: Tue, 21 Aug 2012 12:41:47 +0200 [thread overview]
Message-ID: <503365EB.6000006@supersystem.pl> (raw)
Hi,
I use Raid1 to make backup of the whole system. I remove hot-swap one drive from
the array, and insert another drive. The goal is, that the only activity of a
man is remove and insert the drive. The rest has to be automated.
Every drive, I use for this, has prepared Raid partition and was once added to
array, so the zero block exists and UUID is equal to the working array.
After changing drives, the rebuilding must be initialized (mdadm -add)
But first, it must be discovered, that the device with consistent UUID appeared
in the system with degraded array and is available for us. After such discover,
I can add the device to the degraded array and start rebuilding.
"mdadm --monitor" can recognize that a drive disappeared, but it can't
recognize, thant a drive with consistent UUID appeared!
Or maybye I am wrong and I didn't understand something from mdadm and mdadm.conf?
Now I use for this my own script in crontab and i don't use "mdadm --monitor" at
all because it only partially do what I want.
My question is: Is it possibe to recognize with "mdadm --monitor" that the new
device with consistent UUID appeared? Or if no, do You mean, this feature is
worth to implement?
Sergiusz
ps.
sorry for my english :)
next reply other threads:[~2012-08-21 10:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 10:41 Sergiusz Brzeziński [this message]
2012-08-21 10:44 ` mdadm --monitor: need extra feature? David Brown
2012-08-21 11:51 ` Sergiusz Brzeziński
2012-08-21 12:39 ` Adam Goryachev
2012-08-22 7:14 ` Sergiusz Brzeziński
2012-08-22 7:44 ` NeilBrown
2012-08-22 9:50 ` Sergiusz Brzeziński
[not found] ` <5034B0A2.4080403@websitemanagers.com.au>
2012-08-22 10:50 ` Sergiusz Brzeziński
2012-08-22 10:57 ` Sergiusz Brzeziński
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=503365EB.6000006@supersystem.pl \
--to=sergiusz.brzezinski@supersystem.pl \
--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).