From: Christoph Nelles <evilazrael@evilazrael.de>
To: linux-raid@vger.kernel.org
Subject: Re: RAID5 with 2 drive failure at the same time
Date: Sat, 02 Feb 2013 16:55:03 +0100 [thread overview]
Message-ID: <510D36D7.5050704@evilazrael.de> (raw)
In-Reply-To: <510C6AB6.8040900@turmel.org>
[-- Attachment #1: Type: text/plain, Size: 4888 bytes --]
Hello Phil,
Am 02.02.2013 02:24, schrieb Phil Turmel:
> On 02/01/2013 07:30 PM, Christoph Nelles wrote:
> [trim /]
>
>>> If you're using standard desktop drives then you may be running into
>>> issues with the drive timeout being longer than the kernel's. You need
>>> to reset on or the other to ensure that the drive times out (and is
>>> available for subsequent commands) before the kernel does. Most current
>>> consumer drives don't allow resetting the timeout, but it's worth trying
>>> that first before changing the kernel timeout. For each
>>> drive, do:
>>> smartctl -l scterc,70,70 /dev/sdX
>>> || echo 180 > /sys/block/sdX/device/timeout
>>>
>>
>> Only the WDC Red supports that. The drives on the Marvell Controller all
>> report
>> SCT Error Recovery Control:
>> Read: Disabled
>> Write: Disabled
>
> First, the syntax should have had a backslash on the first line, so that
> a failure on setting SCTERC would fall back to setting a 180 second
> timeout in the driver.
>
> Second, you list three Hitachi Deskstar 7k3000 drives as being on that
> controller. These have supported SCTERC in the past (I have some of
> them) and this is the first I've seen where they don't. Could you
> repeat your smart logs, but with "-x" to get a full report?
You are right, the Hitachis support that. I thought disabled means not
possible. My fault.
Nevertheless I put the smartctl -x -a logs at
http://evilazrael.net/bilder2/logs/smart_xa_20130202.tar.gz
I am currently reading about TLER, and i am wondering why I haven't
heard of that before. Looks like the lower power consumption is not the
only advantage of the WDC Red Edition. Most reviews do not go so deep
into detail.
sdg is a new WDC Red I bought today so all drives from sdg moved one
letter down.
Spent the last three hours analysing why the second onboard controller
does not detect the new HDD. In the end it's a Marvell, IOMMU and linux
driver problem:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1005226
https://bugzilla.kernel.org/show_bug.cgi?id=42679
Marvell = PITA :(
>> To be honest, I don't trust SMART much and prefer a write/read badblocks
>> over SMART tests. But of course i won't do that on a disk which has data
>> on it.
>
> I've never found badblocks to be of use, but smart monitoring for
> relocations is vital information.
>
> Neither SMART nor badblocks will save you if you have a timeout
> mismatch. Enterprise drives work "out-of-the-box" as they have a
> default timeout of 7.0 seconds. Any other drives must have a timeout
> set, or the driver adjusted. Linux drivers default to 30 seconds--not
> enough.
>
> [trim /]
>
>> I think I don't like this part of the discussion ("That won't work").
>
> I've gone back through your data, and part of the story is muddled by
> the timeout mismatch. Your kernel logs show "DRDY" status problems
> before the drives are kicked out. That suggests a drive still in error
> recovery when the kernel driver times out, then not being able to talk
> to the drive to reset the link. Classic no-win situation with desktop
> drives.
I will retry with the changed timeouts and the new disk.
> I didn't see anywhere in your reports whether you've tried "--assemble
> --force". That is always the first tool to revive an array that has
> kicked out drives on such problems.
>
I tried the force-assemble after the first answer from Robin on the ML.
Before that i simply removed and readded the failed drive after doing
running badblocks.
> When you ran badblocks for 2 days, what mode did you use?
destructive write-read (-svw). I canceled after 48 hours as the first
three patterns did not find an error.
> Your descriptions and kernel logs suggest that is /dev/sdg, but the
> "mdadm --examine" reports show /dev/sdg was in the array longer than
> /dev/sdj. Please elaborate.
Where do you read that?
> If you didn't destroy its contents, you should include it in the
> "--assemble --force" attempt. Then, with proper drive timeouts, run a
> "check" scrub. That should fix your UREs.
>
> If you did destroy that drive's contents, you need to clean up the UREs
> on the other drives with dd_rescue, then "--assemble --force" with the
> remaining drives.
ddrescue is running, this will take some hours.
> I think it would be useful to provide a fresh set of "mdadm --examine"
> reports for all member disks, along with a partial listing of
> /dev/disk/by-id/ that shows what serial numbers are assigned to what
> device names.
How do the serial numbers help?
I attached both to this mail.
> I don't think your situation is hopeless.
Thanks :)
Kind Regards
Christoph
--
Christoph Nelles
E-Mail : evilazrael@evilazrael.de
Jabber : eazrael@evilazrael.net ICQ : 78819723
PGP-Key : ID 0x424FB55B on subkeys.pgp.net
or http://evilazrael.net/pgp.txt
[-- Attachment #2: disk_by-id.txt --]
[-- Type: text/plain, Size: 7726 bytes --]
total 0
drwxr-xr-x 2 root root 1680 Feb 2 14:40 ./
drwxr-xr-x 5 root root 100 Feb 2 15:40 ../
lrwxrwxrwx 1 root root 9 Feb 2 15:40 ata-Hitachi_HDS723030ALA640_MK0311YHG248EA -> ../../sdj
lrwxrwxrwx 1 root root 10 Feb 2 15:40 ata-Hitachi_HDS723030ALA640_MK0311YHG248EA-part1 -> ../../sdj1
lrwxrwxrwx 1 root root 9 Feb 2 15:40 ata-Hitachi_HDS723030ALA640_MK0311YHG32VNA -> ../../sdi
lrwxrwxrwx 1 root root 10 Feb 2 15:40 ata-Hitachi_HDS723030ALA640_MK0311YHG32VNA-part1 -> ../../sdi1
lrwxrwxrwx 1 root root 9 Feb 2 15:40 ata-Hitachi_HDS723030ALA640_MK0311YHG6DS3A -> ../../sdh
lrwxrwxrwx 1 root root 10 Feb 2 15:40 ata-Hitachi_HDS723030ALA640_MK0311YHG6DS3A-part1 -> ../../sdh1
lrwxrwxrwx 1 root root 9 Feb 2 15:40 ata-SAMSUNG_SSD_830_Series_S0XYNEAC504407 -> ../../sda
lrwxrwxrwx 1 root root 10 Feb 2 15:40 ata-SAMSUNG_SSD_830_Series_S0XYNEAC504407-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Feb 2 15:40 ata-SAMSUNG_SSD_830_Series_S0XYNEAC504407-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Feb 2 15:40 ata-SAMSUNG_SSD_830_Series_S0XYNEAC504407-part5 -> ../../sda5
lrwxrwxrwx 1 root root 10 Feb 2 15:40 ata-SAMSUNG_SSD_830_Series_S0XYNEAC504407-part6 -> ../../sda6
lrwxrwxrwx 1 root root 10 Feb 2 15:40 ata-SAMSUNG_SSD_830_Series_S0XYNEAC504407-part7 -> ../../sda7
lrwxrwxrwx 1 root root 10 Feb 2 15:40 ata-SAMSUNG_SSD_830_Series_S0XYNEAC504407-part8 -> ../../sda8
lrwxrwxrwx 1 root root 9 Feb 2 15:40 ata-ST3000DM001-9YN166_Z1F0D9AW -> ../../sdb
lrwxrwxrwx 1 root root 10 Feb 2 15:40 ata-ST3000DM001-9YN166_Z1F0D9AW-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 9 Feb 2 15:40 ata-WDC_WD30EFRX-68AX9N0_WD-WMC1T1267036 -> ../../sde
lrwxrwxrwx 1 root root 10 Feb 2 15:40 ata-WDC_WD30EFRX-68AX9N0_WD-WMC1T1267036-part1 -> ../../sde1
lrwxrwxrwx 1 root root 9 Feb 2 14:53 ata-WDC_WD30EFRX-68AX9N0_WD-WMC1T2001070 -> ../../sdg
lrwxrwxrwx 1 root root 9 Feb 2 15:40 ata-WDC_WD30EURS-63R8UY0_WD-WCAWZ2236938 -> ../../sdf
lrwxrwxrwx 1 root root 10 Feb 2 15:40 ata-WDC_WD30EURS-63R8UY0_WD-WCAWZ2236938-part1 -> ../../sdf1
lrwxrwxrwx 1 root root 9 Feb 2 15:40 ata-WDC_WD30EZRS-00J99B0_WD-WCAWZ0319650 -> ../../sdd
lrwxrwxrwx 1 root root 10 Feb 2 15:40 ata-WDC_WD30EZRS-00J99B0_WD-WCAWZ0319650-part1 -> ../../sdd1
lrwxrwxrwx 1 root root 9 Feb 2 15:40 ata-WDC_WD30EZRX-00MMMB0_WD-WCAWZ1394037 -> ../../sdk
lrwxrwxrwx 1 root root 10 Feb 2 15:40 ata-WDC_WD30EZRX-00MMMB0_WD-WCAWZ1394037-part1 -> ../../sdk1
lrwxrwxrwx 1 root root 9 Feb 2 15:40 ata-WDC_WD30EZRX-00MMMB0_WD-WMAWZ0236402 -> ../../sdc
lrwxrwxrwx 1 root root 10 Feb 2 15:40 ata-WDC_WD30EZRX-00MMMB0_WD-WMAWZ0236402-part1 -> ../../sdc1
lrwxrwxrwx 1 root root 9 Feb 2 15:40 scsi-SATA_Hitachi_HDS7230_MK0311YHG248EA -> ../../sdj
lrwxrwxrwx 1 root root 10 Feb 2 15:40 scsi-SATA_Hitachi_HDS7230_MK0311YHG248EA-part1 -> ../../sdj1
lrwxrwxrwx 1 root root 9 Feb 2 15:40 scsi-SATA_Hitachi_HDS7230_MK0311YHG32VNA -> ../../sdi
lrwxrwxrwx 1 root root 10 Feb 2 15:40 scsi-SATA_Hitachi_HDS7230_MK0311YHG32VNA-part1 -> ../../sdi1
lrwxrwxrwx 1 root root 9 Feb 2 15:40 scsi-SATA_Hitachi_HDS7230_MK0311YHG6DS3A -> ../../sdh
lrwxrwxrwx 1 root root 10 Feb 2 15:40 scsi-SATA_Hitachi_HDS7230_MK0311YHG6DS3A-part1 -> ../../sdh1
lrwxrwxrwx 1 root root 9 Feb 2 15:40 scsi-SATA_SAMSUNG_SSD_830S0XYNEAC504407 -> ../../sda
lrwxrwxrwx 1 root root 10 Feb 2 15:40 scsi-SATA_SAMSUNG_SSD_830S0XYNEAC504407-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Feb 2 15:40 scsi-SATA_SAMSUNG_SSD_830S0XYNEAC504407-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Feb 2 15:40 scsi-SATA_SAMSUNG_SSD_830S0XYNEAC504407-part5 -> ../../sda5
lrwxrwxrwx 1 root root 10 Feb 2 15:40 scsi-SATA_SAMSUNG_SSD_830S0XYNEAC504407-part6 -> ../../sda6
lrwxrwxrwx 1 root root 10 Feb 2 15:40 scsi-SATA_SAMSUNG_SSD_830S0XYNEAC504407-part7 -> ../../sda7
lrwxrwxrwx 1 root root 10 Feb 2 15:40 scsi-SATA_SAMSUNG_SSD_830S0XYNEAC504407-part8 -> ../../sda8
lrwxrwxrwx 1 root root 9 Feb 2 15:40 scsi-SATA_ST3000DM001-9YN_Z1F0D9AW -> ../../sdb
lrwxrwxrwx 1 root root 10 Feb 2 15:40 scsi-SATA_ST3000DM001-9YN_Z1F0D9AW-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 9 Feb 2 15:40 scsi-SATA_WDC_WD30EFRX-68_WD-WMC1T1267036 -> ../../sde
lrwxrwxrwx 1 root root 10 Feb 2 15:40 scsi-SATA_WDC_WD30EFRX-68_WD-WMC1T1267036-part1 -> ../../sde1
lrwxrwxrwx 1 root root 9 Feb 2 14:53 scsi-SATA_WDC_WD30EFRX-68_WD-WMC1T2001070 -> ../../sdg
lrwxrwxrwx 1 root root 9 Feb 2 15:40 scsi-SATA_WDC_WD30EURS-63_WD-WCAWZ2236938 -> ../../sdf
lrwxrwxrwx 1 root root 10 Feb 2 15:40 scsi-SATA_WDC_WD30EURS-63_WD-WCAWZ2236938-part1 -> ../../sdf1
lrwxrwxrwx 1 root root 9 Feb 2 15:40 scsi-SATA_WDC_WD30EZRS-00_WD-WCAWZ0319650 -> ../../sdd
lrwxrwxrwx 1 root root 10 Feb 2 15:40 scsi-SATA_WDC_WD30EZRS-00_WD-WCAWZ0319650-part1 -> ../../sdd1
lrwxrwxrwx 1 root root 9 Feb 2 15:40 scsi-SATA_WDC_WD30EZRX-00_WD-WCAWZ1394037 -> ../../sdk
lrwxrwxrwx 1 root root 10 Feb 2 15:40 scsi-SATA_WDC_WD30EZRX-00_WD-WCAWZ1394037-part1 -> ../../sdk1
lrwxrwxrwx 1 root root 9 Feb 2 15:40 scsi-SATA_WDC_WD30EZRX-00_WD-WMAWZ0236402 -> ../../sdc
lrwxrwxrwx 1 root root 10 Feb 2 15:40 scsi-SATA_WDC_WD30EZRX-00_WD-WMAWZ0236402-part1 -> ../../sdc1
lrwxrwxrwx 1 root root 9 Feb 2 14:40 usb-Generic_2.0_Reader_-0_00000001-0:0 -> ../../sdl
lrwxrwxrwx 1 root root 9 Feb 2 14:40 usb-Generic_2.0_Reader_-1_00000001-0:1 -> ../../sdm
lrwxrwxrwx 1 root root 10 Feb 2 14:40 usb-Generic_2.0_Reader_-1_00000001-0:1-part1 -> ../../sdm1
lrwxrwxrwx 1 root root 9 Feb 2 14:40 usb-Generic_2.0_Reader_-2_00000001-0:2 -> ../../sdn
lrwxrwxrwx 1 root root 9 Feb 2 15:40 wwn-0x5000c5003f73d3f3 -> ../../sdb
lrwxrwxrwx 1 root root 10 Feb 2 15:40 wwn-0x5000c5003f73d3f3-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 9 Feb 2 15:40 wwn-0x5000cca225c0f8c7 -> ../../sdj
lrwxrwxrwx 1 root root 10 Feb 2 15:40 wwn-0x5000cca225c0f8c7-part1 -> ../../sdj1
lrwxrwxrwx 1 root root 9 Feb 2 15:40 wwn-0x5000cca225c167d9 -> ../../sdi
lrwxrwxrwx 1 root root 10 Feb 2 15:40 wwn-0x5000cca225c167d9-part1 -> ../../sdi1
lrwxrwxrwx 1 root root 9 Feb 2 15:40 wwn-0x5000cca225c2ea12 -> ../../sdh
lrwxrwxrwx 1 root root 10 Feb 2 15:40 wwn-0x5000cca225c2ea12-part1 -> ../../sdh1
lrwxrwxrwx 1 root root 9 Feb 2 15:40 wwn-0x50014ee0adb3a14b -> ../../sdc
lrwxrwxrwx 1 root root 10 Feb 2 15:40 wwn-0x50014ee0adb3a14b-part1 -> ../../sdc1
lrwxrwxrwx 1 root root 9 Feb 2 14:53 wwn-0x50014ee0ae2d738f -> ../../sdg
lrwxrwxrwx 1 root root 9 Feb 2 15:40 wwn-0x50014ee20645bfea -> ../../sdk
lrwxrwxrwx 1 root root 10 Feb 2 15:40 wwn-0x50014ee20645bfea-part1 -> ../../sdk1
lrwxrwxrwx 1 root root 9 Feb 2 15:40 wwn-0x50014ee2b04244d4 -> ../../sdd
lrwxrwxrwx 1 root root 10 Feb 2 15:40 wwn-0x50014ee2b04244d4-part1 -> ../../sdd1
lrwxrwxrwx 1 root root 9 Feb 2 15:40 wwn-0x50014ee2b1b314a2 -> ../../sdf
lrwxrwxrwx 1 root root 10 Feb 2 15:40 wwn-0x50014ee2b1b314a2-part1 -> ../../sdf1
lrwxrwxrwx 1 root root 9 Feb 2 15:40 wwn-0x50014ee6ad9ea39b -> ../../sde
lrwxrwxrwx 1 root root 10 Feb 2 15:40 wwn-0x50014ee6ad9ea39b-part1 -> ../../sde1
lrwxrwxrwx 1 root root 9 Feb 2 15:40 wwn-0x5002538043584d30 -> ../../sda
lrwxrwxrwx 1 root root 10 Feb 2 15:40 wwn-0x5002538043584d30-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Feb 2 15:40 wwn-0x5002538043584d30-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Feb 2 15:40 wwn-0x5002538043584d30-part5 -> ../../sda5
lrwxrwxrwx 1 root root 10 Feb 2 15:40 wwn-0x5002538043584d30-part6 -> ../../sda6
lrwxrwxrwx 1 root root 10 Feb 2 15:40 wwn-0x5002538043584d30-part7 -> ../../sda7
lrwxrwxrwx 1 root root 10 Feb 2 15:40 wwn-0x5002538043584d30-part8 -> ../../sda8
[-- Attachment #3: mdadm_examine.txt --]
[-- Type: text/plain, Size: 7468 bytes --]
/dev/sdb1:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : 6b21b3ed:d39d5a54:d4939113:77851cb6
Name : router:0 (local to host router)
Creation Time : Fri Apr 27 20:25:04 2012
Raid Level : raid5
Raid Devices : 9
Avail Dev Size : 5860529039 (2794.52 GiB 3000.59 GB)
Array Size : 46884229120 (22356.14 GiB 24004.73 GB)
Used Dev Size : 5860528640 (2794.52 GiB 3000.59 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : clean
Device UUID : 29c62776:e9c58ce6:1c6e9ab1:046ac411
Update Time : Fri Feb 1 23:02:02 2013
Checksum : be4a3d6b - correct
Events : 27742
Layout : left-symmetric
Chunk Size : 64K
Device Role : Active device 6
Array State : A.AAA.AAA ('A' == active, '.' == missing)
/dev/sdc1:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : 6b21b3ed:d39d5a54:d4939113:77851cb6
Name : router:0 (local to host router)
Creation Time : Fri Apr 27 20:25:04 2012
Raid Level : raid5
Raid Devices : 9
Avail Dev Size : 5860529039 (2794.52 GiB 3000.59 GB)
Array Size : 46884229120 (22356.14 GiB 24004.73 GB)
Used Dev Size : 5860528640 (2794.52 GiB 3000.59 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : clean
Device UUID : 6e591e9f:7a5c6fc6:33750743:c7d05b5e
Update Time : Fri Feb 1 23:02:02 2013
Checksum : a527d515 - correct
Events : 27742
Layout : left-symmetric
Chunk Size : 64K
Device Role : Active device 0
Array State : A.AAA.AAA ('A' == active, '.' == missing)
/dev/sdd1:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : 6b21b3ed:d39d5a54:d4939113:77851cb6
Name : router:0 (local to host router)
Creation Time : Fri Apr 27 20:25:04 2012
Raid Level : raid5
Raid Devices : 9
Avail Dev Size : 5860529039 (2794.52 GiB 3000.59 GB)
Array Size : 46884229120 (22356.14 GiB 24004.73 GB)
Used Dev Size : 5860528640 (2794.52 GiB 3000.59 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : clean
Device UUID : 4d229bb4:053902db:c4b278ef:d56b567f
Update Time : Fri Feb 1 23:02:02 2013
Checksum : 9ca35322 - correct
Events : 27742
Layout : left-symmetric
Chunk Size : 64K
Device Role : Active device 3
Array State : A.AAA.AAA ('A' == active, '.' == missing)
/dev/sde1:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : 6b21b3ed:d39d5a54:d4939113:77851cb6
Name : router:0 (local to host router)
Creation Time : Fri Apr 27 20:25:04 2012
Raid Level : raid5
Raid Devices : 9
Avail Dev Size : 5860529039 (2794.52 GiB 3000.59 GB)
Array Size : 46884229120 (22356.14 GiB 24004.73 GB)
Used Dev Size : 5860528640 (2794.52 GiB 3000.59 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : clean
Device UUID : 7acacfa5:a805babf:60bb525c:ef450aa4
Update Time : Fri Feb 1 23:02:02 2013
Checksum : 41daaad - correct
Events : 27742
Layout : left-symmetric
Chunk Size : 64K
Device Role : Active device 8
Array State : A.AAA.AAA ('A' == active, '.' == missing)
/dev/sdf1:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : 6b21b3ed:d39d5a54:d4939113:77851cb6
Name : router:0 (local to host router)
Creation Time : Fri Apr 27 20:25:04 2012
Raid Level : raid5
Raid Devices : 9
Avail Dev Size : 5860529039 (2794.52 GiB 3000.59 GB)
Array Size : 46884229120 (22356.14 GiB 24004.73 GB)
Used Dev Size : 5860528640 (2794.52 GiB 3000.59 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : clean
Device UUID : 68047273:c10a8f48:e447728f:1f8a7b32
Update Time : Fri Feb 1 23:02:02 2013
Checksum : 1c25ba66 - correct
Events : 27742
Layout : left-symmetric
Chunk Size : 64K
Device Role : Active device 7
Array State : A.AAA.AAA ('A' == active, '.' == missing)
/dev/sdh1:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : 6b21b3ed:d39d5a54:d4939113:77851cb6
Name : router:0 (local to host router)
Creation Time : Fri Apr 27 20:25:04 2012
Raid Level : raid5
Raid Devices : 9
Avail Dev Size : 5860529039 (2794.52 GiB 3000.59 GB)
Array Size : 46884229120 (22356.14 GiB 24004.73 GB)
Used Dev Size : 5860528640 (2794.52 GiB 3000.59 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : clean
Device UUID : a1b16284:321fcdd0:93993ff5:832eee3a
Update Time : Fri Feb 1 23:02:02 2013
Checksum : 23947226 - correct
Events : 27742
Layout : left-symmetric
Chunk Size : 64K
Device Role : spare
Array State : A.AAA.AAA ('A' == active, '.' == missing)
/dev/sdi1:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : 6b21b3ed:d39d5a54:d4939113:77851cb6
Name : router:0 (local to host router)
Creation Time : Fri Apr 27 20:25:04 2012
Raid Level : raid5
Raid Devices : 9
Avail Dev Size : 5860529039 (2794.52 GiB 3000.59 GB)
Array Size : 46884229120 (22356.14 GiB 24004.73 GB)
Used Dev Size : 5860528640 (2794.52 GiB 3000.59 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : clean
Device UUID : 4e6931d9:13edc311:8e4bd316:e8c3379d
Update Time : Fri Feb 1 23:02:02 2013
Checksum : 3d373f0c - correct
Events : 27742
Layout : left-symmetric
Chunk Size : 64K
Device Role : Active device 2
Array State : A.AAA.AAA ('A' == active, '.' == missing)
/dev/sdj1:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : 6b21b3ed:d39d5a54:d4939113:77851cb6
Name : router:0 (local to host router)
Creation Time : Fri Apr 27 20:25:04 2012
Raid Level : raid5
Raid Devices : 9
Avail Dev Size : 5860529039 (2794.52 GiB 3000.59 GB)
Array Size : 46884229120 (22356.14 GiB 24004.73 GB)
Used Dev Size : 5860528640 (2794.52 GiB 3000.59 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : clean
Device UUID : 09c3515e:f6c0931d:55bcd591:3d9d58b6
Update Time : Fri Feb 1 23:02:02 2013
Checksum : 624ab6c8 - correct
Events : 27742
Layout : left-symmetric
Chunk Size : 64K
Device Role : Active device 4
Array State : A.AAA.AAA ('A' == active, '.' == missing)
/dev/sdk1:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : 6b21b3ed:d39d5a54:d4939113:77851cb6
Name : router:0 (local to host router)
Creation Time : Fri Apr 27 20:25:04 2012
Raid Level : raid5
Raid Devices : 9
Avail Dev Size : 5860529039 (2794.52 GiB 3000.59 GB)
Array Size : 46884229120 (22356.14 GiB 24004.73 GB)
Used Dev Size : 5860528640 (2794.52 GiB 3000.59 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : clean
Device UUID : 7023df83:d890ce04:fc28652e:094adffe
Update Time : Fri Feb 1 22:48:11 2013
Checksum : 5431fd40 - correct
Events : 27738
Layout : left-symmetric
Chunk Size : 64K
Device Role : Active device 5
Array State : AAAAAAAAA ('A' == active, '.' == missing)
next prev parent reply other threads:[~2013-02-02 15:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 10:42 RAID5 with 2 drive failure at the same time Christoph Nelles
2013-01-31 11:38 ` Robin Hill
2013-01-31 13:15 ` Christoph Nelles
2013-01-31 13:45 ` Robin Hill
2013-01-31 17:46 ` Chris Murphy
[not found] ` <510ABC1E.6060308@evilazrael.de>
2013-01-31 21:19 ` Chris Murphy
2013-01-31 22:10 ` Robin Hill
2013-01-31 22:40 ` Chris Murphy
2013-01-31 22:48 ` Chris Murphy
2013-02-01 13:34 ` Robin Hill
2013-02-01 17:27 ` Chris Murphy
2013-02-01 19:57 ` Robin Hill
2013-02-02 0:30 ` Christoph Nelles
2013-02-02 1:24 ` Phil Turmel
2013-02-02 15:55 ` Christoph Nelles [this message]
2013-02-02 20:34 ` Chris Murphy
2013-02-02 23:56 ` Phil Turmel
2013-02-03 1:22 ` Phil Turmel
2013-02-03 15:56 ` Christoph Nelles
2013-02-03 21:59 ` Robin Hill
2013-02-10 20:48 ` Christoph Nelles
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=510D36D7.5050704@evilazrael.de \
--to=evilazrael@evilazrael.de \
--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).