* RAID5 reshape problems
@ 2009-03-25 18:31 Stefan G. Weichinger
2009-03-25 20:11 ` Stefan G. Weichinger
2009-03-25 22:13 ` Neil Brown
0 siblings, 2 replies; 7+ messages in thread
From: Stefan G. Weichinger @ 2009-03-25 18:31 UTC (permalink / raw)
To: linux-raid
Could someone *please* help me out?
I have a problematic RAID5 and don't know how to proceed.
Situation:
gentoo linux, 32bit, 2.6.25-gentoo-r8
mdadm-2.6.4-r1
Initially 4 x 1TB SATA-disks, partitioned.
SCSI storage controller: LSI Logic / Symbios Logic SAS1068 PCI-X
Fusion-MPT SAS (rev 01)
/dev/md2 contained of /dev/sd{abcd}4 ...
2 x 1 TB added (hotplugged), disks detected fine, partitioned
Added /dev/sd{ef}4 to /dev/md2, triggered grow to 6 raid-devices.
Started fine. Projected end of reshape ~3100 minutes, started at around
17h local time. Maybe it accelerated while I was out and userload decreased.
--
Then sdf failed:
Mar 25 17:23:47 horde sd 0:0:5:0: [sdf] CDB: cdb[0]=0x28: 28 00 01 5d de
a4 00 00 18 00
Mar 25 17:23:47 horde mptscsih: ioc0: target reset: FAILED (sc=eae51800)
Mar 25 17:23:47 horde mptscsih: ioc0: attempting bus reset! (sc=eae51800)
Mar 25 17:23:47 horde sd 0:0:5:0: [sdf] CDB: cdb[0]=0x28: 28 00 01 5d de
a4 00 00 18 00
Mar 25 17:23:47 horde mptsas: ioc0: removing sata device, channel 0, id
6, phy 6
Mar 25 17:23:47 horde port-0:5: mptsas: ioc0: delete port (5)
Mar 25 17:23:47 horde sd 0:0:5:0: [sdf] Synchronizing SCSI cache
Mar 25 17:23:47 horde mptscsih: ioc0: bus reset: SUCCESS (sc=eae51800)
Mar 25 17:23:47 horde mptscsih: ioc0: attempting host reset! (sc=eae51800)
Mar 25 17:23:47 horde mptbase: ioc0: Initiating recovery
Mar 25 17:23:47 horde mptscsih: ioc0: host reset: SUCCESS (sc=eae51800)
Mar 25 17:23:47 horde sd 0:0:5:0: Device offlined - not ready after
error recovery
Mar 25 17:23:47 horde sd 0:0:5:0: Device offlined - not ready after
error recovery
Mar 25 17:23:47 horde sd 0:0:5:0: Device offlined - not ready after
error recovery
Mar 25 17:23:47 horde sd 0:0:5:0: Device offlined - not ready after
error recovery
Mar 25 17:23:47 horde sd 0:0:5:0: Device offlined - not ready after
error recovery
Mar 25 17:23:47 horde sd 0:0:5:0: Device offlined - not ready after
error recovery
Mar 25 17:23:47 horde sd 0:0:5:0: Device offlined - not ready after
error recovery
Mar 25 17:23:47 horde sd 0:0:5:0: Device offlined - not ready after
error recovery
Mar 25 17:23:47 horde sd 0:0:5:0: [sdf] Result: hostbyte=0x01
driverbyte=0x00
Mar 25 17:23:47 horde end_request: I/O error, dev sdf, sector 42380636
Mar 25 17:23:47 horde raid5: Disk failure on sdf4, disabling device.
Operation continuing on 5 devices
Mar 25 17:23:47 horde sd 0:0:5:0: [sdf] Result: hostbyte=0x01
driverbyte=0x00
Mar 25 17:23:47 horde end_request: I/O error, dev sdf, sector 42379612
Mar 25 17:23:47 horde sd 0:0:5:0: [sdf] Result: hostbyte=0x01
driverbyte=0x00
Mar 25 17:23:47 horde end_request: I/O error, dev sdf, sector 22929100
Mar 25 17:23:47 horde raid5:md2: read error not correctable (sector
5000560 on sdf4).
Mar 25 17:23:47 horde sd 0:0:5:0: [sdf] Result: hostbyte=0x01
driverbyte=0x00
Mar 25 17:23:47 horde end_request: I/O error, dev sdf, sector 22929092
Mar 25 17:23:47 horde raid5:md2: read error not correctable (sector
5000552 on sdf4).
Mar 25 17:23:47 horde sd 0:0:5:0: [sdf] Result: hostbyte=0x01
driverbyte=0x00
Mar 25 17:23:47 horde end_request: I/O error, dev sdf, sector 22929084
Mar 25 17:23:47 horde raid5:md2: read error not correctable (sector
5000544 on sdf4).
Mar 25 17:23:47 horde sd 0:0:5:0: [sdf] Result: hostbyte=0x01
driverbyte=0x00
Mar 25 17:23:47 horde end_request: I/O error, dev sdf, sector 22929108
Mar 25 17:23:47 horde raid5:md2: read error not correctable (sector
5000568 on sdf4).
Mar 25 17:23:47 horde sd 0:0:5:0: [sdf] Result: hostbyte=0x01
driverbyte=0x00
Mar 25 17:23:47 horde end_request: I/O error, dev sdf, sector 22928988
Mar 25 17:23:47 horde raid5:md2: read error not correctable (sector
5000448 on sdf4).
Mar 25 17:23:47 horde raid5:md2: read error not correctable (sector
5000456 on sdf4).
Mar 25 17:23:47 horde raid5:md2: read error not correctable (sector
5000464 on sdf4).
Mar 25 17:23:47 horde raid5:md2: read error not correctable (sector
5000472 on sdf4).
Mar 25 17:23:47 horde raid5:md2: read error not correctable (sector
5000480 on sdf4).
Mar 25 17:23:47 horde raid5:md2: read error not correctable (sector
5000488 on sdf4).
Mar 25 17:23:47 horde raid5:md2: read error not correctable (sector
5000496 on sdf4).
Mar 25 17:23:47 horde raid5:md2: read error not correctable (sector
5000504 on sdf4).
Mar 25 17:23:47 horde raid5:md2: read error not correctable (sector
5000512 on sdf4).
Mar 25 17:23:47 horde sd 0:0:5:0: [sdf] Result: hostbyte=0x01
driverbyte=0x00
Mar 25 17:23:47 horde end_request: I/O error, dev sdf, sector 22929060
Mar 25 17:23:47 horde raid5:md2: read error not correctable (sector
5000520 on sdf4).
Mar 25 17:23:47 horde raid5:md2: read error not correctable (sector
5000528 on sdf4).
Mar 25 17:23:47 horde raid5:md2: read error not correctable (sector
5000536 on sdf4).
Mar 25 17:23:47 horde end_request: I/O error, dev sdf, sector 1953519836
Mar 25 17:23:47 horde md: super_written gets error=-5, uptodate=0
Mar 25 17:23:47 horde sd 0:0:5:0: [sdf] Result: hostbyte=0x01
driverbyte=0x00
Mar 25 17:23:47 horde md: md2: reshape done.
Mar 25 17:23:47 horde mdadm: Fail event detected on md device /dev/md2,
component device /dev/sdf4
----
Now I have a system with load ~77 ...
I don't get answers to "cat /proc/mdstat" ...
We removed sdf, which didn't decrease the load.
top doesn't show any particular hog, CPUs near idle, disks as well.
"mdadm -D" doesn't give me answers.
Only this:
# mdadm -E /dev/sda4
/dev/sda4:
Magic : a92b4efc
Version : 00.91.00
UUID : 2e27c42d:40936d45:53eb5abe:265a9668
Creation Time : Wed Oct 22 19:43:13 2008
Raid Level : raid5
Used Dev Size : 967795648 (922.96 GiB 991.02 GB)
Array Size : 4838978240 (4614.81 GiB 4955.11 GB)
Raid Devices : 6
Total Devices : 6
Preferred Minor : 2
Reshape pos'n : 61125760 (58.29 GiB 62.59 GB)
Delta Devices : 2 (4->6)
Update Time : Wed Mar 25 17:23:47 2009
State : active
Active Devices : 5
Working Devices : 5
Failed Devices : 1
Spare Devices : 0
Checksum : 65f12171 - correct
Events : 0.8247
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 0 8 4 0 active sync /dev/sda4
0 0 8 4 0 active sync /dev/sda4
1 1 8 20 1 active sync /dev/sdb4
2 2 8 36 2 active sync /dev/sdc4
3 3 8 52 3 active sync /dev/sdd4
4 4 0 0 4 faulty removed
5 5 8 68 5 active sync /dev/sde4
---
/dev/md2 is the single PV in an LVM-VG, I don't get output from
vgdisplay, pvdisplay.
But I see the mounted LVs, and I am able to browse the data.
The OS itself is on /dev/md1 which only contains /dev/sd{abcd}3 , so no
new/faulty disks included.
---
My question:
How to proceed? Is the raid OK? May I try a reboot and everything is OK
or NOT? Is it possible that the reshape with now only 5 disks was
finished so much faster?
I sh** my pants as there is important data there. Yes, backups exist ...
but the downtime ...
Please help me out so that I can fix this one and find sleep this night ...
Thanks a lot in advance!
Stefan
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: RAID5 reshape problems
2009-03-25 18:31 RAID5 reshape problems Stefan G. Weichinger
@ 2009-03-25 20:11 ` Stefan G. Weichinger
2009-03-25 22:13 ` Neil Brown
1 sibling, 0 replies; 7+ messages in thread
From: Stefan G. Weichinger @ 2009-03-25 20:11 UTC (permalink / raw)
To: linux-raid
Just as an addition while I am waiting desparately ...
here the section of dmesg:
sd 0:0:5:0: Device offlined - not ready after error recovery
sd 0:0:5:0: Device offlined - not ready after error recovery
sd 0:0:5:0: Device offlined - not ready after error recovery
sd 0:0:5:0: Device offlined - not ready after error recovery
sd 0:0:5:0: [sdf] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdf, sector 42380636
raid5: Disk failure on sdf4, disabling device. Operation continuing on 5
devices
sd 0:0:5:0: [sdf] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdf, sector 42379612
sd 0:0:5:0: [sdf] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdf, sector 22929100
raid5:md2: read error not correctable (sector 5000560 on sdf4).
sd 0:0:5:0: [sdf] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdf, sector 22929092
raid5:md2: read error not correctable (sector 5000552 on sdf4).
sd 0:0:5:0: [sdf] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdf, sector 22929084
raid5:md2: read error not correctable (sector 5000544 on sdf4).
sd 0:0:5:0: [sdf] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdf, sector 22929108
raid5:md2: read error not correctable (sector 5000568 on sdf4).
sd 0:0:5:0: [sdf] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdf, sector 22928988
raid5:md2: read error not correctable (sector 5000448 on sdf4).
raid5:md2: read error not correctable (sector 5000456 on sdf4).
raid5:md2: read error not correctable (sector 5000464 on sdf4).
raid5:md2: read error not correctable (sector 5000472 on sdf4).
raid5:md2: read error not correctable (sector 5000480 on sdf4).
raid5:md2: read error not correctable (sector 5000488 on sdf4).
raid5:md2: read error not correctable (sector 5000496 on sdf4).
raid5:md2: read error not correctable (sector 5000504 on sdf4).
raid5:md2: read error not correctable (sector 5000512 on sdf4).
sd 0:0:5:0: [sdf] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdf, sector 22929060
raid5:md2: read error not correctable (sector 5000520 on sdf4).
raid5:md2: read error not correctable (sector 5000528 on sdf4).
raid5:md2: read error not correctable (sector 5000536 on sdf4).
end_request: I/O error, dev sdf, sector 1953519836
md: super_written gets error=-5, uptodate=0
sd 0:0:5:0: [sdf] Result: hostbyte=0x01 driverbyte=0x00
md: md2: reshape done.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: RAID5 reshape problems
2009-03-25 18:31 RAID5 reshape problems Stefan G. Weichinger
2009-03-25 20:11 ` Stefan G. Weichinger
@ 2009-03-25 22:13 ` Neil Brown
2009-03-25 22:43 ` Stefan G. Weichinger
1 sibling, 1 reply; 7+ messages in thread
From: Neil Brown @ 2009-03-25 22:13 UTC (permalink / raw)
To: lists; +Cc: linux-raid
On Wednesday March 25, lists@xunil.at wrote:
>
> Could someone *please* help me out?
>
> I have a problematic RAID5 and don't know how to proceed.
>
> Situation:
>
> gentoo linux, 32bit, 2.6.25-gentoo-r8
>
> mdadm-2.6.4-r1
>
> Initially 4 x 1TB SATA-disks, partitioned.
>
> SCSI storage controller: LSI Logic / Symbios Logic SAS1068 PCI-X
> Fusion-MPT SAS (rev 01)
>
> /dev/md2 contained of /dev/sd{abcd}4 ...
>
> 2 x 1 TB added (hotplugged), disks detected fine, partitioned
>
> Added /dev/sd{ef}4 to /dev/md2, triggered grow to 6 raid-devices.
>
> Started fine. Projected end of reshape ~3100 minutes, started at around
> 17h local time. Maybe it accelerated while I was out and userload decreased.
>
> --
>
> Then sdf failed:
>
> Mar 25 17:23:47 horde sd 0:0:5:0: [sdf] CDB: cdb[0]=0x28: 28 00 01 5d de
> a4 00 00 18 00
....
> Mar 25 17:23:47 horde md: md2: reshape done.
> Mar 25 17:23:47 horde mdadm: Fail event detected on md device /dev/md2,
> component device /dev/sdf4
>
>
On getting a device failure, md will abort the reshape. It should
then notice that a reshape needs to be completed and start again.
I guess it didn't.
>
> ----
>
>
> Now I have a system with load ~77 ...
>
> I don't get answers to "cat /proc/mdstat" ...
>
> We removed sdf, which didn't decrease the load.
>
> top doesn't show any particular hog, CPUs near idle, disks as well.
With a load of 77 you should see something odd in
ps axgu
either processes in status 'R' or 'D'.
>
> "mdadm -D" doesn't give me answers.
Must be some sort of deadlock....
>
> Only this:
>
> # mdadm -E /dev/sda4
> /dev/sda4:
> Magic : a92b4efc
> Version : 00.91.00
> UUID : 2e27c42d:40936d45:53eb5abe:265a9668
> Creation Time : Wed Oct 22 19:43:13 2008
> Raid Level : raid5
> Used Dev Size : 967795648 (922.96 GiB 991.02 GB)
> Array Size : 4838978240 (4614.81 GiB 4955.11 GB)
> Raid Devices : 6
> Total Devices : 6
> Preferred Minor : 2
>
> Reshape pos'n : 61125760 (58.29 GiB 62.59 GB)
> Delta Devices : 2 (4->6)
>
> Update Time : Wed Mar 25 17:23:47 2009
> State : active
> Active Devices : 5
> Working Devices : 5
> Failed Devices : 1
> Spare Devices : 0
> Checksum : 65f12171 - correct
> Events : 0.8247
>
> Layout : left-symmetric
> Chunk Size : 64K
>
> Number Major Minor RaidDevice State
> this 0 8 4 0 active sync /dev/sda4
>
> 0 0 8 4 0 active sync /dev/sda4
> 1 1 8 20 1 active sync /dev/sdb4
> 2 2 8 36 2 active sync /dev/sdc4
> 3 3 8 52 3 active sync /dev/sdd4
> 4 4 0 0 4 faulty removed
> 5 5 8 68 5 active sync /dev/sde4
>
This looks good. The devices knows that it is in the middle of a
reshape, and knows how far along it is. After a reboot it should just
pick up where it left off.
>
> ---
>
>
> /dev/md2 is the single PV in an LVM-VG, I don't get output from
> vgdisplay, pvdisplay.
>
> But I see the mounted LVs, and I am able to browse the data.
>
> The OS itself is on /dev/md1 which only contains /dev/sd{abcd}3 , so no
> new/faulty disks included.
>
> ---
>
> My question:
>
> How to proceed? Is the raid OK? May I try a reboot and everything is OK
> or NOT? Is it possible that the reshape with now only 5 disks was
> finished so much faster?
The raid is OK. It is, of course, degraded now and if another device
fails you will lose data. Reboot should be perfectly safe. However
you might need to re-assemble the array using the "--force" flag.
This is safe.
The reshape didn't finish. It is only up to
> Reshape pos'n : 61125760 (58.29 GiB 62.59 GB)
NeilBrown
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: RAID5 reshape problems
2009-03-25 22:13 ` Neil Brown
@ 2009-03-25 22:43 ` Stefan G. Weichinger
2009-03-26 6:58 ` Stefan G. Weichinger
0 siblings, 1 reply; 7+ messages in thread
From: Stefan G. Weichinger @ 2009-03-25 22:43 UTC (permalink / raw)
To: linux-raid
Neil Brown schrieb:
>> "mdadm -D" doesn't give me answers.
>
> Must be some sort of deadlock....
Yes ...
your suggested ps-command showed numerous instances of hanging
smbd-processes, cronjobs etc.
I feel a bit ashamed to not have taken more daemons offline for doing
that ... but I couldn't foresee the fact that the hotplug-tray would be
full of dust and that the owner of the box wouldn't see that ...
It is very likely that the disk is OK itself, just the connection might
have been too dirty!
>> State : active
>> Active Devices : 5
>> Working Devices : 5
>> Failed Devices : 1
>> Spare Devices : 0
>> Checksum : 65f12171 - correct
>> Events : 0.8247
>>
>> Layout : left-symmetric
>> Chunk Size : 64K
>>
>> Number Major Minor RaidDevice State
>> this 0 8 4 0 active sync /dev/sda4
>>
>> 0 0 8 4 0 active sync /dev/sda4
>> 1 1 8 20 1 active sync /dev/sdb4
>> 2 2 8 36 2 active sync /dev/sdc4
>> 3 3 8 52 3 active sync /dev/sdd4
>> 4 4 0 0 4 faulty removed
>> 5 5 8 68 5 active sync /dev/sde4
>>
>
> This looks good. The devices knows that it is in the middle of a
> reshape, and knows how far along it is. After a reboot it should just
> pick up where it left off.
Sounds gooood ...
> The raid is OK. It is, of course, degraded now and if another device
> fails you will lose data. Reboot should be perfectly safe. However
> you might need to re-assemble the array using the "--force" flag.
> This is safe.
> The reshape didn't finish. It is only up to
>> Reshape pos'n : 61125760 (58.29 GiB 62.59 GB)
ok ... thanks for your feedback, thanks a lot.
Sorry that I called it a "problematic RAID5" ... your code seems not to
be the problem here :-)
I try a remote reboot, I am more than 100 kms away from that server.
It seems to take forever now to reboot, I can still ping it while ssh
doesn't work anymore.
Might take till tomorrow when the owner comes to office again that he
will be able to reboot the box via console.
At least I am somehow more confident now that we won't lose data.
I avoid thinking of having to re-add that /dev/sdf again, and the
pvresize is also still ahead of me.
*sigh*
;-)
Thanks again, Stefan
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: RAID5 reshape problems
2009-03-25 22:43 ` Stefan G. Weichinger
@ 2009-03-26 6:58 ` Stefan G. Weichinger
2009-03-26 10:20 ` Stefan G. Weichinger
0 siblings, 1 reply; 7+ messages in thread
From: Stefan G. Weichinger @ 2009-03-26 6:58 UTC (permalink / raw)
Cc: linux-raid
Stefan G. Weichinger schrieb:
> Might take till tomorrow when the owner comes to office again that he
> will be able to reboot the box via console.
>
> At least I am somehow more confident now that we won't lose data.
Update: a hard reboot worked, the raid was visible but inactive.
We re-added the now checked sdf (in a completely cleaned server) and the
raid was still inactive. In the end I had to re-assemble the md-device
with 5 out of 6 devices, right now it rebuilds:
# cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4]
md1 : active raid5 sde3[3](S) sdd3[2] sdb3[1] sda3[0]
17591040 blocks level 5, 64k chunk, algorithm 2 [3/3] [UUU]
md2 : active raid5 sde4[3] sdd4[2] sdc4[5] sdb4[1] sda4[0]
2903386944 blocks super 0.91 level 5, 64k chunk, algorithm 2 [6/5]
[UUUU_U]
[>....................] reshape = 1.9% (18408064/967795648)
finish=1479.2min speed=10696K/sec
# mdadm -D /dev/md2
/dev/md2:
Version : 00.91.03
Creation Time : Wed Oct 22 19:43:13 2008
Raid Level : raid5
Array Size : 2903386944 (2768.89 GiB 2973.07 GB)
Used Dev Size : 967795648 (922.96 GiB 991.02 GB)
Raid Devices : 6
Total Devices : 5
Preferred Minor : 2
Persistence : Superblock is persistent
Update Time : Thu Mar 26 07:56:33 2009
State : clean, degraded, recovering
Active Devices : 5
Working Devices : 5
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 64K
Reshape Status : 1% complete
Delta Devices : 2, (4->6)
UUID : 2e27c42d:40936d45:53eb5abe:265a9668
Events : 0.12576
Number Major Minor RaidDevice State
0 8 4 0 active sync /dev/sda4
1 8 20 1 active sync /dev/sdb4
2 8 52 2 active sync /dev/sdd4
3 8 68 3 active sync /dev/sde4
4 0 0 4 removed
5 8 36 5 active sync /dev/sdc4
---
I assume that I will simply have to add /dev/sdf4 then ??
Or again "add" and then "grow" ?
The PV/VG/LVs all are valid, time to try to relax a bit now.
Thanks, Neil,
Stefan
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: RAID5 reshape problems
2009-03-26 6:58 ` Stefan G. Weichinger
@ 2009-03-26 10:20 ` Stefan G. Weichinger
2009-03-27 18:11 ` RAID5 reshape problems : SOLVED Stefan G. Weichinger
0 siblings, 1 reply; 7+ messages in thread
From: Stefan G. Weichinger @ 2009-03-26 10:20 UTC (permalink / raw)
To: linux-raid
Stefan G. Weichinger schrieb:
> I assume that I will simply have to add /dev/sdf4 then ??
> Or again "add" and then "grow" ?
Did a "mdadm --re-add /dev/md2 /dev/sdf4", now it looks like:
# mdadm -D /dev/md2
/dev/md2:
Version : 00.91.03
Creation Time : Wed Oct 22 19:43:13 2008
Raid Level : raid5
Array Size : 2903386944 (2768.89 GiB 2973.07 GB)
Used Dev Size : 967795648 (922.96 GiB 991.02 GB)
Raid Devices : 6
Total Devices : 6
Preferred Minor : 2
Persistence : Superblock is persistent
Update Time : Thu Mar 26 11:18:48 2009
State : clean, degraded, recovering
Active Devices : 5
Working Devices : 6
Failed Devices : 0
Spare Devices : 1
Layout : left-symmetric
Chunk Size : 64K
Reshape Status : 14% complete
Delta Devices : 2, (4->6)
UUID : 2e27c42d:40936d45:53eb5abe:265a9668
Events : 0.96428
Number Major Minor RaidDevice State
0 8 4 0 active sync /dev/sda4
1 8 20 1 active sync /dev/sdb4
2 8 52 2 active sync /dev/sdd4
3 8 68 3 active sync /dev/sde4
4 0 0 4 removed
5 8 36 5 active sync /dev/sdc4
6 8 84 - spare /dev/sdf4
Looks very OK to me.
*phew*
I will wait until it isn't degraded anymore before I do the "pvresize".
Thanks all, Stefan
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: RAID5 reshape problems : SOLVED
2009-03-26 10:20 ` Stefan G. Weichinger
@ 2009-03-27 18:11 ` Stefan G. Weichinger
0 siblings, 0 replies; 7+ messages in thread
From: Stefan G. Weichinger @ 2009-03-27 18:11 UTC (permalink / raw)
To: lists; +Cc: linux-raid
Stefan G. Weichinger schrieb:
> I will wait until it isn't degraded anymore before I do the "pvresize".
Just for the records (maybe I need to google this myself someday ;) ):
The whole process finished this afternoon, with all 6 disks in the
raid5. The following pvresize worked without a problem as well.
So everything is fine again, it really seems that dust was the main
problem here ...
Thanks, Stefan
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2009-03-27 18:11 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-03-25 18:31 RAID5 reshape problems Stefan G. Weichinger
2009-03-25 20:11 ` Stefan G. Weichinger
2009-03-25 22:13 ` Neil Brown
2009-03-25 22:43 ` Stefan G. Weichinger
2009-03-26 6:58 ` Stefan G. Weichinger
2009-03-26 10:20 ` Stefan G. Weichinger
2009-03-27 18:11 ` RAID5 reshape problems : SOLVED Stefan G. Weichinger
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.