Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
To: Ben Bucksch <linux.news@bucksch.org>
Cc: linux-raid@vger.kernel.org, Brad Campbell <lists2009@fnarfbargle.com>
Subject: Re: md RAID5: Disk wrongly marked "spare", need to force re-add it
Date: Sun, 21 Apr 2013 13:07:52 +0200 (CEST)	[thread overview]
Message-ID: <17077622.2.1366542472549.JavaMail.root@zimbra> (raw)
In-Reply-To: <5173A159.70202@bucksch.org>

> Brad Campbell wrote, On 21.04.2013 09:23:
> > As others have already told you, md does not go randomly kicking
> > drives from arrays. Your system had a failure of some kind which
> > caused the loss of two drives.
> 
> You ignore the facts and do "mi mi mi" in face of bugs reports. 2
> different arrays lost 1 drive, both at the same time at reboot after
> the
> OS upgrade, and both drives are working fine. Facts.
> 
> And even *if* they had a temporary error, my case shows why it's a
> *bug*
> to kick them out of the array. And it's a *bug* to not let me put them
> back in with data. Tons of other people have suffered dataloss because
> of various temporary, easily recoverable problems and these 2 bugs.
> 
> People like you are the reason why people like me suffer dataloss.

Well, just restore from backup. Shouldn't be too hard.

Vennlige hilsener / Best regards

roy
--
Roy Sigurd Karlsbakk
(+47) 98013356
roy@karlsbakk.net
http://blogg.karlsbakk.net/
GPG Public key: http://karlsbakk.net/roysigurdkarlsbakk.pubkey.txt
--
I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det er et elementært imperativ for alle pedagoger å unngå eksessiv anvendelse av idiomer med xenotyp etymologi. I de fleste tilfeller eksisterer adekvate og relevante synonymer på norsk.
--
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

  parent reply	other threads:[~2013-04-21 11:07 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
2013-04-21 22:00                           ` Ben Bucksch
2013-04-21 11:07                       ` Roy Sigurd Karlsbakk [this message]
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=17077622.2.1366542472549.JavaMail.root@zimbra \
    --to=roy@karlsbakk.net \
    --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