From: David Brown <david@westcontrol.com>
To: linux-raid@vger.kernel.org
Subject: Re: potentially lost largeish raid5 array..
Date: Fri, 23 Sep 2011 09:06:35 +0200 [thread overview]
Message-ID: <j5hbc3$rh4$1@dough.gmane.org> (raw)
In-Reply-To: <201109222310.28684.tfjellstrom@shaw.ca>
On 23/09/2011 07:10, Thomas Fjellstrom wrote:
> On September 22, 2011, Roman Mamedov wrote:
>> On Thu, 22 Sep 2011 22:49:12 -0600
>>
>> Thomas Fjellstrom<tfjellstrom@shaw.ca> wrote:
>>> Now I guess the question is, how to get that last drive back in? would:
>>>
>>> mdadm --re-add /dev/md1 /dev/sdi
>>>
>>> work?
>>
>> It should, or at least it will not harm anything, but keep in mind that
>> simply trying to continue using the array (raid5 with a largeish member
>> count) on a flaky controller card is akin to playing with fire.
>
> Yeah, I think I won't be using the 3.0 kernel after tonight. At least the
> older kernel's would just lock up the card and not cause md to boot the disks
> one at a time.
>
> I /really really/ wish the driver for this card was more stable, but you deal
> with what you've got (in my case a $100 2 port SAS/8 port SATA card). I've
> been rather lucky so far it seems, I hope my luck keeps up long enough for
> either the driver to stabilize, me to get a new card, or at the very least, to
> get a third drive for my backup array, so if the main array does go down, I
> have a recent daily sync.
>
My own (limited) experience with SAS is that you /don't/ get what you
pay for. I had a SAS drive on a server (actually a firewall) as the
server salesman had persuaded me that it was more reliable than SATA,
and therefore a good choice for a critical machine. The SAS controller
card died recently. I replaced it with two SATA drives connected
directly to the motherboard, with md raid - much more reliable and much
cheaper (and faster too).
next prev parent reply other threads:[~2011-09-23 7:06 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 1:50 potentially lost largeish raid5 array Thomas Fjellstrom
2011-09-23 4:32 ` NeilBrown
2011-09-23 4:49 ` Thomas Fjellstrom
2011-09-23 4:58 ` Roman Mamedov
2011-09-23 5:10 ` Thomas Fjellstrom
2011-09-23 7:06 ` David Brown [this message]
2011-09-23 7:37 ` Thomas Fjellstrom
2011-09-23 12:56 ` Stan Hoeppner
2011-09-23 13:28 ` David Brown
2011-09-23 16:22 ` Thomas Fjellstrom
2011-09-23 23:24 ` Stan Hoeppner
2011-09-24 0:11 ` Thomas Fjellstrom
2011-09-24 12:17 ` Stan Hoeppner
2011-09-24 13:11 ` (unknown) Tomáš Dulík
2011-09-24 15:16 ` potentially lost largeish raid5 array David Brown
2011-09-24 16:38 ` Stan Hoeppner
2011-09-25 13:03 ` David Brown
2011-09-25 14:39 ` Stan Hoeppner
2011-09-25 15:18 ` David Brown
2011-09-25 23:58 ` Stan Hoeppner
2011-09-26 10:51 ` David Brown
2011-09-26 19:52 ` Stan Hoeppner
2011-09-26 20:29 ` David Brown
2011-09-26 23:28 ` Krzysztof Adamski
2011-09-27 3:53 ` Stan Hoeppner
2011-09-24 17:48 ` Thomas Fjellstrom
2011-09-24 5:59 ` Mikael Abrahamsson
2011-09-24 17:53 ` Thomas Fjellstrom
2011-09-25 18:07 ` Robert L Mathews
2011-09-26 6:08 ` Mikael Abrahamsson
2011-09-26 2:26 ` Krzysztof Adamski
2011-09-23 5:11 ` NeilBrown
2011-09-23 5:22 ` Thomas Fjellstrom
2011-09-23 8:09 ` Thomas Fjellstrom
2011-09-23 9:15 ` NeilBrown
2011-09-23 16:26 ` Thomas Fjellstrom
2011-09-25 9:37 ` NeilBrown
2011-09-24 21:57 ` Aapo Laine
2011-09-25 9:18 ` Kristleifur Daðason
2011-09-25 10:10 ` NeilBrown
2011-10-01 23:21 ` Aapo Laine
2011-10-02 17:00 ` Aapo Laine
2011-10-05 2:13 ` NeilBrown
2011-10-05 2:06 ` NeilBrown
2011-11-05 12:17 ` Alexander Lyakas
2011-11-06 21:58 ` NeilBrown
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='j5hbc3$rh4$1@dough.gmane.org' \
--to=david@westcontrol.com \
--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 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.