From: Phil Turmel <philip@turmel.org>
To: "Wols Lists" <antlists@youngman.org.uk>,
"André Teichert" <andre_teichert@gmx.de>,
linux-raid@vger.kernel.org
Subject: Re: mdadm raid5 dropped 2 disks
Date: Sat, 6 Feb 2016 09:03:27 -0500 [thread overview]
Message-ID: <56B5FD2F.9060005@turmel.org> (raw)
In-Reply-To: <56B5DD2B.50307@youngman.org.uk>
Good morning André, Wol,
On 02/06/2016 06:46 AM, Wols Lists wrote:
> On 06/02/16 10:54, André Teichert wrote:
>> glad it worked. Will save lsdrv and hope never to use it. Create new
>> backupplan!
>
> Please DO use lsdrv. EVERY time you create or change the config of an
> array, run it and save the info somewhere safe.
Yes, lsdrv is intended to document a running system for later use when
not running. Especially serial numbers, device names, UUIDs, and layer
relationships. It is still helpful later, but naturally some info can
be missed.
> Neil has just stepped down as maintainer and Phil is now "one of the
> team",
That's a bit of a stretch. I'm not maintaining any code and I'm
volunteering on the list as I have in the past.
> he wrote that utility specifically to help in recovering crashed
> arrays. If anything goes wrong and you've got that data to hand, it'll
> make their lives much easier to help you.
Yes, array configuration documentation is critical to recovery.
Phil
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-02-06 14:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 10:30 mdadm raid5 dropped 2 disks André Teichert
2016-02-06 9:45 ` Wols Lists
2016-02-06 10:54 ` André Teichert
2016-02-06 11:46 ` Wols Lists
2016-02-06 14:03 ` Phil Turmel [this message]
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=56B5FD2F.9060005@turmel.org \
--to=philip@turmel.org \
--cc=andre_teichert@gmx.de \
--cc=antlists@youngman.org.uk \
--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).