From: "Stefan G. Weichinger" <lists@xunil.at>
To: linux-raid@vger.kernel.org
Subject: Re: Re-adding disks to RAID6 in a Fujitsu NAS: old mdadm?
Date: Wed, 27 Jun 2012 13:34:48 +0200 [thread overview]
Message-ID: <4FEAEFD8.4070605@xunil.at> (raw)
In-Reply-To: <4FEADDCC.2070905@xunil.at>
[-- Attachment #1: Type: text/plain, Size: 404 bytes --]
Am 27.06.2012 12:17, schrieb Stefan G. Weichinger:
> Am 26.06.2012 15:57, schrieb Stefan G. Weichinger:
>
>> I would really really like to avoid to rebuild that array ...
>>
>> Thanks in advance, looking forward to your hints, Stefan!
>
> Noone any thoughts on this?
> Correction: thoughts alone wouldn't write a posting ;-)
more infos in attachment (will it get, as requested off-list.
thanks ...
[-- Attachment #2: report --]
[-- Type: text/plain, Size: 4680 bytes --]
/dev/sda3:
Magic : a92b4efc
Version : 00.90.00
UUID : 938aa1a7:a216603a:d46d31fa:4faee42a
Creation Time : Thu Aug 11 21:19:43 2011
Raid Level : raid6
Used Dev Size : 1951945600 (1861.52 GiB 1998.79 GB)
Array Size : 3903891200 (3723.04 GiB 3997.58 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 0
Update Time : Fri Nov 4 00:13:42 2011
State : active
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Checksum : 143cd05d - correct
Events : 0.248094
Chunk Size : 64K
Number Major Minor RaidDevice State
this 1 8 19 1 active sync /dev/sdb3
0 0 8 3 0 active sync /dev/sda3
1 1 8 19 1 active sync /dev/sdb3
2 2 8 35 2 active sync /dev/sdc3
3 3 8 51 3 active sync /dev/sdd3
/dev/sdb3:
Magic : a92b4efc
Version : 00.90.00
UUID : 938aa1a7:a216603a:d46d31fa:4faee42a
Creation Time : Thu Aug 11 21:19:43 2011
Raid Level : raid6
Used Dev Size : 1951945600 (1861.52 GiB 1998.79 GB)
Array Size : 3903891200 (3723.04 GiB 3997.58 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 0
Update Time : Fri Nov 4 00:13:42 2011
State : active
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Checksum : 143cd04b - correct
Events : 0.248094
Chunk Size : 64K
Number Major Minor RaidDevice State
this 0 8 3 0 active sync /dev/sda3
0 0 8 3 0 active sync /dev/sda3
1 1 8 19 1 active sync /dev/sdb3
2 2 8 35 2 active sync /dev/sdc3
3 3 8 51 3 active sync /dev/sdd3
/dev/sdc3:
Magic : a92b4efc
Version : 00.90.00
UUID : 938aa1a7:a216603a:d46d31fa:4faee42a
Creation Time : Thu Aug 11 21:19:43 2011
Raid Level : raid6
Used Dev Size : 1951945600 (1861.52 GiB 1998.79 GB)
Array Size : 3903891200 (3723.04 GiB 3997.58 GB)
Raid Devices : 4
Total Devices : 2
Preferred Minor : 0
Update Time : Wed Jun 27 13:32:30 2012
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 1
Spare Devices : 0
Checksum : 15f80804 - correct
Events : 0.4430040
Chunk Size : 64K
Number Major Minor RaidDevice State
this 2 8 35 2 active sync /dev/sdc3
0 0 0 0 0 removed
1 1 0 0 1 faulty removed
2 2 8 35 2 active sync /dev/sdc3
3 3 8 51 3 active sync /dev/sdd3
/dev/sdd3:
Magic : a92b4efc
Version : 00.90.00
UUID : 938aa1a7:a216603a:d46d31fa:4faee42a
Creation Time : Thu Aug 11 21:19:43 2011
Raid Level : raid6
Used Dev Size : 1951945600 (1861.52 GiB 1998.79 GB)
Array Size : 3903891200 (3723.04 GiB 3997.58 GB)
Raid Devices : 4
Total Devices : 2
Preferred Minor : 0
Update Time : Wed Jun 27 13:32:30 2012
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 1
Spare Devices : 0
Checksum : 15f80816 - correct
Events : 0.4430040
Chunk Size : 64K
Number Major Minor RaidDevice State
this 3 8 51 3 active sync /dev/sdd3
0 0 0 0 0 removed
1 1 0 0 1 faulty removed
2 2 8 35 2 active sync /dev/sdc3
3 3 8 51 3 active sync /dev/sdd3
/dev/md0:
Version : 00.90.03
Creation Time : Thu Aug 11 21:19:43 2011
Raid Level : raid6
Array Size : 3903891200 (3723.04 GiB 3997.58 GB)
Used Dev Size : 1951945600 (1861.52 GiB 1998.79 GB)
Raid Devices : 4
Total Devices : 2
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Wed Jun 27 13:32:30 2012
State : clean, degraded
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Chunk Size : 64K
UUID : 938aa1a7:a216603a:d46d31fa:4faee42a
Events : 0.4430040
Number Major Minor RaidDevice State
0 0 0 0 removed
1 0 0 1 removed
2 8 35 2 active sync /dev/sdc3
3 8 51 3 active sync /dev/sdd3
next prev parent reply other threads:[~2012-06-27 11:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 13:57 Re-adding disks to RAID6 in a Fujitsu NAS: old mdadm? Stefan G. Weichinger
2012-06-27 10:17 ` Stefan G. Weichinger
2012-06-27 11:34 ` Stefan G. Weichinger [this message]
2012-06-27 11:38 ` Stefan G. Weichinger
2012-06-28 6:32 ` NeilBrown
2012-06-28 8:59 ` Stefan G. Weichinger
2012-06-28 9:14 ` Stefan G. Weichinger
2012-06-28 9:23 ` Stefan G. Weichinger
2012-06-28 11:22 ` NeilBrown
2012-06-28 15:56 ` Stefan G. Weichinger
2012-06-28 18:25 ` Stefan G. Weichinger
2012-06-28 21:36 ` NeilBrown
2012-06-29 8:18 ` Stefan G. Weichinger
2012-07-02 8:30 ` Stefan G. Weichinger
2012-06-28 21:39 ` NeilBrown
2012-06-28 9:39 ` NeilBrown
2012-06-28 9:42 ` Stefan G. Weichinger
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=4FEAEFD8.4070605@xunil.at \
--to=lists@xunil.at \
--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.