From: Brad Campbell <lists2009@fnarfbargle.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: linux-raid@vger.kernel.org
Subject: Re: Possible to rescue SW Raid5 with 2 missing Disks
Date: Fri, 15 Feb 2013 20:12:44 +0800 [thread overview]
Message-ID: <511E263C.6070704@fnarfbargle.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1302151220060.32644@uplift.swm.pp.se>
On 15/02/13 19:23, Mikael Abrahamsson wrote:
> On Fri, 15 Feb 2013, Brad Campbell wrote:
>
>> To the point I've been ready to submit a patch for --assume-clean along the lines of what hdparm
>> does and makes you also attach --please-destroy-my-disk before it'll work.
>
> Yes, I think this is an excellent idea. It should have --please-destroy-my-disk, and if there are
> existing superblocks, it should save the contents of mdadm --examine before overwriting or
> zero:ing them.
Please don't get me wrong. There is no nice way of protecting fools from themselves short of
revoking their license to breed, it's just from my severely opinionated viewpoint that this looks
like a sane idea. I'm quite prepared to be slapped, and in fact probably need it.
> --assemble --force should list the drive event count and say which drives have differing event
> counts and ask for confirmation that this is really what the operator wants to do. If the event
> count differs more than 50 (or some other value), there should be a requirement for
> --please-destroy-my-array to be added :P
>
>> --assume-clean is great for those that need it, but for the great majority who rely on google and
>> wikis it's a data-destroyer.
>
This is not a sleight on Neil and/or mdadm. The tools are wonderful, it's those that compose
permanent articles without a full understanding that need adjusting. Unfortunately it's also those
that don't really care as long as it drives page hits or reputation.
Brad (the unpleasant)
next prev parent reply other threads:[~2013-02-15 12:12 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 21:39 Possible to rescue SW Raid5 with 2 missing Disks Dragon
2013-02-15 9:57 ` Mikael Abrahamsson
2013-02-15 11:14 ` Brad Campbell
2013-02-15 11:23 ` Mikael Abrahamsson
2013-02-15 12:12 ` Brad Campbell [this message]
2013-02-15 12:34 ` Mikael Abrahamsson
-- strict thread matches above, loose matches on Subject: below --
2013-03-03 23:09 Dragon
2013-03-03 21:59 Dragon
2013-02-27 7:14 Dragon
2013-02-21 15:36 Dragon
2013-02-20 8:54 Dragon
2013-02-20 7:44 Dragon
2013-02-20 8:06 ` Mikael Abrahamsson
2013-02-19 20:36 Dragon
2013-02-19 15:19 Dragon
2013-02-19 17:48 ` Phil Turmel
2013-02-19 18:32 ` Roy Sigurd Karlsbakk
2013-02-18 12:13 Dragon
2013-02-15 15:41 Dragon
2013-02-16 5:06 ` Mikael Abrahamsson
2013-02-15 12:59 Dragon
2013-02-15 14:51 ` Mikael Abrahamsson
2013-02-15 9:46 Dragon
2013-02-14 21:00 Dragon
2013-02-14 21:11 ` Robin Hill
2013-02-15 0:59 ` Dave Cundiff
2013-02-14 15:01 Dragon
2013-02-14 17:09 ` Mikael Abrahamsson
2013-02-14 17:18 ` Dave Cundiff
2013-02-14 14:31 Dragon
2013-02-14 14:39 ` Mikael Abrahamsson
2013-02-10 21:27 Dragon
2013-02-08 9:17 Dragon
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=511E263C.6070704@fnarfbargle.com \
--to=lists2009@fnarfbargle.com \
--cc=linux-raid@vger.kernel.org \
--cc=swmike@swm.pp.se \
/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.