From: Brad Campbell <brad@wasp.net.au>
To: RAID Linux <linux-raid@vger.kernel.org>
Subject: Information gathering script
Date: Wed, 24 Mar 2010 23:10:13 +0800 [thread overview]
Message-ID: <4BAA2B55.8040504@wasp.net.au> (raw)
G'day all,
Having just dropped a drive (it turns out 1TB SATA drives don't bounce) that belonged in my 10 drive
RAID-6 and having replaced it this afternoon, I had a thought.
When things go wrong (particularly those nasty things that cause the sick feeling in the pit of your
stomach) the best help is always available give the right information.
If there was a script that one could run when things were healthy that dumped all the relevant
information for safe keeping, would it reduce the nightmare that is recovering a broken raid?
I'd imagine an mdadm --examine on each component of a RAID, partition tables and perhaps a --detail
on each md device. Is there anything else that might be handy that could be dumped to a verbose
output just in case?
Is there already such a thing?
Regards,
Brad
--
Dolphins are so intelligent that within a few weeks they can
train Americans to stand at the edge of the pool and throw them
fish.
next reply other threads:[~2010-03-24 15:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 15:10 Brad Campbell [this message]
2010-03-24 15:51 ` Information gathering script Kristleifur Daðason
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=4BAA2B55.8040504@wasp.net.au \
--to=brad@wasp.net.au \
--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).