From: Roberto Nunnari <roberto.nunnari@supsi.ch>
To: Roberto Nunnari <roberto.nunnari@supsi.ch>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: replacing drives
Date: Tue, 30 Apr 2013 16:28:39 +0200 [thread overview]
Message-ID: <517FD517.70507@supsi.ch> (raw)
In-Reply-To: <517FCFB2.3010900@supsi.ch>
Roberto Nunnari wrote:
> Robin Hill wrote:
>> On Tue Apr 30, 2013 at 03:17:30PM +0200, Roberto Nunnari wrote:
>>>> - grow the arrays to 4 members (this avoids any loss of redundancy)
>>> now the next step.. that's a raid1 array.. is it possible to grow the
>>> arrays to 4 members?
>>>
>> Yes, there's no problem with running RAID1 arrays with more than two
>> mirrors (with md anyway) - they're all identical so it doesn't really
>> make any difference how many you have.
>>
>> Cheers,
>> Robin
>
> ok.. it's rebuilding.. I started with md0.. I'll wait it finishes and
> then do md1(8GB) and after that, md2(almost 2TB).. for now it seems to
> be going well, isn't it?
>
> # mdadm -D /dev/md0
> /dev/md0:
> Version : 00.90
> Creation Time : Fri Apr 22 08:20:49 2011
> Raid Level : raid1
> Array Size : 48827328 (46.57 GiB 50.00 GB)
> Used Dev Size : 48827328 (46.57 GiB 50.00 GB)
> Raid Devices : 4
> Total Devices : 4
> Preferred Minor : 0
> Persistence : Superblock is persistent
>
> Update Time : Tue Apr 30 16:01:40 2013
> State : clean, degraded, recovering
> Active Devices : 2
> Working Devices : 4
> Failed Devices : 0
> Spare Devices : 2
>
> Rebuild Status : 15% complete
>
> UUID : 1158db16:ee1fcafc:b6fab772:d376c644
> Events : 0.964
>
> Number Major Minor RaidDevice State
> 0 8 1 0 active sync /dev/sda1
> 1 8 33 1 active sync /dev/sdc1
> 4 8 49 2 spare rebuilding /dev/sdd1
> 5 8 17 3 spare rebuilding /dev/sdb1
>
>
> Robi
rebuilt and clean! hehehe
Robi
next prev parent reply other threads:[~2013-04-30 14:28 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 14:27 replacing drives Roberto Nunnari
2013-04-26 15:36 ` Tregaron Bayly
2013-04-26 15:42 ` Keith Keller
2013-04-26 15:53 ` Robin Hill
2013-04-30 13:17 ` Roberto Nunnari
2013-04-30 13:20 ` Mikael Abrahamsson
2013-04-30 14:11 ` Roberto Nunnari
2013-04-30 14:22 ` Robin Hill
2013-04-30 14:40 ` Mikael Abrahamsson
2013-04-30 14:27 ` Roberto Nunnari
2013-04-30 14:39 ` Roberto Nunnari
2013-04-30 14:42 ` Mikael Abrahamsson
2013-04-30 15:10 ` Roberto Nunnari
2013-04-30 15:11 ` Phil Turmel
2013-04-30 15:39 ` Roberto Spadim
2013-05-01 1:55 ` Brad Campbell
2013-05-01 15:06 ` Roberto Nunnari
2013-05-01 18:14 ` Roberto Spadim
2013-05-02 17:49 ` Roy Sigurd Karlsbakk
2013-05-02 17:43 ` Roy Sigurd Karlsbakk
2013-04-30 13:45 ` Robin Hill
2013-04-30 14:05 ` Roberto Nunnari
2013-04-30 14:28 ` Roberto Nunnari [this message]
2013-04-30 15:19 ` Roberto Nunnari
2013-05-02 13:56 ` Roberto Nunnari
2013-05-02 14:54 ` Robin Hill
2013-05-02 15:00 ` Roberto Nunnari
2013-05-03 16:28 ` Roberto Nunnari
2013-05-06 11:30 ` Roberto Nunnari
2013-05-07 7:53 ` Robin Hill
2013-05-07 10:22 ` Roberto Nunnari
2013-05-08 14:19 ` Roberto Nunnari
2013-05-08 15:10 ` Robin Hill
2013-05-08 16:05 ` Roberto Nunnari
2013-05-08 17:01 ` Robin Hill
2013-05-08 17:20 ` Roberto Nunnari
2013-05-10 21:35 ` Roberto Nunnari
2013-04-26 22:20 ` Roberto Nunnari
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=517FD517.70507@supsi.ch \
--to=roberto.nunnari@supsi.ch \
--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).