Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: Brad Campbell <lists2009@fnarfbargle.com>
Cc: Ben Bucksch <linux.news@bucksch.org>, linux-raid@vger.kernel.org
Subject: Re: md RAID5: Disk wrongly marked "spare", need to force re-add it
Date: Sun, 21 Apr 2013 14:17:06 -0400	[thread overview]
Message-ID: <51742D22.2080601@turmel.org> (raw)
In-Reply-To: <5173C353.6080008@fnarfbargle.com>

Hi Brad,

I'm sorry you've been sucked into exchanges with this troll.  (I spotted
the attitude in the original post.)  A couple comments below:

On 04/21/2013 06:45 AM, Brad Campbell wrote:

> Again : "Good news: In my desperation, I now ran the following dangerous
> command: mdadm --create /dev/md0 --assume-clean --level=raid5 -n 8
> --chunk=64 --layout=left-symmetric --metadata=0.90 /dev/sdj missing
> /dev/sdl /dev/sd[mopnq]"

I did find it interesting that Ben tried this on his own, given that's
the very advice he demanded not be given in his OP.

> How did you verify you had your disks in the correct order? Where did
> that command line come from?

Ben's shell skills seem to match his interpersonal communication skills
(weak).  The construct /dev/sd[mopnq] expands as if it was specified
/dev/sd[mnopq].  His misunderstanding of bracket syntax has wrecked his
array.  If he had used braces, or spelled out all the devices, he'd
probably be fine right now.

If he tries again, with this in mind, he might still be fine.  (I
haven't checked if his attempted device order was correct, though.)  If
I was inclined to respond directly to him, I'd further suggest he review
the list archives for "error recovery", "timeouts", and "scrubbing".  He
might learn enough to not suffer so much next time.

> This will be my last post on the subject. I pointed you at a path of
> action in my last post.

If Ben's attitude had moderated in following posts, I might have set
aside my first impression and cut him some slack.  That's a significant
consideration when non-native English is involved.  But it's clearly not
the case here.

My first *and* last post on this topic.

Phil

  reply	other threads:[~2013-04-21 18:17 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-12 20:08 md RAID5: Disk wrongly marked "spare", need to force re-add it Ben Bucksch
2013-04-13 14:19 ` Roy Sigurd Karlsbakk
2013-04-14 22:40 ` Oliver Schinagl
2013-04-15  1:34   ` Ben Bucksch
2013-04-14 17:30     ` Oliver Schinagl
2013-04-15 10:26       ` Ben Bucksch
2013-04-14 18:16         ` Oliver Schinagl
2013-04-18 13:17         ` Ben Bucksch
2013-04-18 13:58           ` Maarten
2013-04-19 22:56             ` linux.news
2013-04-20  1:26               ` Ben Bucksch
2013-04-20  1:53                 ` Ben Bucksch
2013-04-21  7:23                   ` Brad Campbell
2013-04-21  8:20                     ` Ben Bucksch
2013-04-21 10:45                       ` Brad Campbell
2013-04-21 18:17                         ` Phil Turmel [this message]
2013-04-21 22:00                           ` Ben Bucksch
2013-04-21 11:07                       ` Roy Sigurd Karlsbakk
2013-04-21 21:50                   ` NeilBrown
2013-04-21 21:46                 ` NeilBrown
2013-04-18 14:18           ` Roy Sigurd Karlsbakk
2013-04-18 14:38           ` Robin Hill
2013-04-20 13:44             ` Oliver Schinagl

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=51742D22.2080601@turmel.org \
    --to=philip@turmel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=linux.news@bucksch.org \
    --cc=lists2009@fnarfbargle.com \
    /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