Am Montag, den 18.08.2008, 19:54 -0300 schrieb martin f krafft:
> > You need to tell me exactly what you did. What you describe is not
> > possible. I don't contest you are seeing a problem, but I have done
> > these steps hundreds of times without any problem ever.
As I found the bug I even didn't know that you have a `call for testers'
on PTS. This was totally by accident.
I never use mdadm much or RAID at all.
With my little understanding of it, I just think that this is wrong.
RAID 10 with 1 fully synced disk and 3 spare.
In the case of `mdadm' I am a stupid user.
I should have said in the report `Probable I did something stupid, non
realistic and wrong' :)
My mail today morning was probable a bit too short, because I assumed
the question is `how do you get into this situation'.
Am Dienstag, den 19.08.2008, 08:29 +0200 schrieb Felix Zielcke:
> Ok, just did it now from scratch.
[...]
> fz-vm:~# mdadm -Q --detail /dev/md0
Attached is now the full output of everything inclusive my little `vm'
ssh alias and logout message :)
I did it now again like that.
After that `mdadm -Q --detail /dev/md0':
fz-vm:~# mdadm -A
--update=resync /dev/md0 /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1
mdadm: device /dev/md0 already active - cannot assemble it
fz-vm:~# mdadm --grow -l10 -n4 /dev/md0
mdadm: raid10 array /dev/md0 cannot be reshaped.
fz-vm:~# mdadm -S /dev/md0
mdadm: stopped /dev/md0
fz-vm:~# mdadm -R /dev/md0
mdadm: failed to run array /dev/md0: Invalid argument
fz-vm:~# mdadm -A
--update=resync /dev/md0 /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1
mdadm: /dev/md0 assembled from 1 drive and 3 spares - not enough to
start the array.
So maybe I should have used `mdadm --zero-superblock' between `mdadm
-r /dev/sdc1' and mdadm `mdadm -a /dev/sdc1' ?
Or maybe I should have done that `mdadm -A --update=resync' in between?
As far as I remember I did this before I reported the bug after I
removed the first disk (sdc1)
But for a stupid user like me in that case, it looks like something
should be changed.
As you can see I just removed and added the disks and didn't check in
between if they get added as spare.
Only in the end I saw `Oh I shouldn't do this' :D
[EMAIL PROTECTED]:~$ vm
Linux fz-vm 2.6.27-rc3 #4 SMP Sun Aug 17 18:32:18 CEST 2008 x86_64
Last login: Tue Aug 19 15:37:01 2008 from 192.168.70.1
fz-vm:~# sfdisk -d /dev/sda|sfdisk /dev/sdc
Checking that no-one is using this disk right now ...
OK
Disk /dev/sdc: 1044 cylinders, 255 heads, 63 sectors/track
sfdisk: ERROR: sector 0 does not have an msdos signature
/dev/sdc: unrecognized partition table type
Old situation:
No partitions found
New situation:
Units = sectors of 512 bytes, counting from 0
Device Boot Start End #sectors Id System
/dev/sdc1 63 16771859 16771797 83 Linux
/dev/sdc2 0 - 0 0 Empty
/dev/sdc3 0 - 0 0 Empty
/dev/sdc4 0 - 0 0 Empty
Warning: no primary partition is marked bootable (active)
This does not matter for LILO, but the DOS MBR will not boot this disk.
Successfully wrote the new partition table
Re-reading the partition table ...
If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)
to zero the first 512 bytes: dd if=/dev/zero of=/dev/foo7 bs=512 count=1
(See fdisk(8).)
fz-vm:~# sfdisk -d /dev/sda|sfdisk /dev/sdd
Checking that no-one is using this disk right now ...
OK
Disk /dev/sdd: 1044 cylinders, 255 heads, 63 sectors/track
sfdisk: ERROR: sector 0 does not have an msdos signature
/dev/sdd: unrecognized partition table type
Old situation:
No partitions found
New situation:
Units = sectors of 512 bytes, counting from 0
Device Boot Start End #sectors Id System
/dev/sdd1 63 16771859 16771797 83 Linux
/dev/sdd2 0 - 0 0 Empty
/dev/sdd3 0 - 0 0 Empty
/dev/sdd4 0 - 0 0 Empty
Warning: no primary partition is marked bootable (active)
This does not matter for LILO, but the DOS MBR will not boot this disk.
Successfully wrote the new partition table
Re-reading the partition table ...
If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)
to zero the first 512 bytes: dd if=/dev/zero of=/dev/foo7 bs=512 count=1
(See fdisk(8).)
fz-vm:~# sfdisk -d /dev/sda|sfdisk /dev/sde
Checking that no-one is using this disk right now ...
OK
Disk /dev/sde: 1044 cylinders, 255 heads, 63 sectors/track
sfdisk: ERROR: sector 0 does not have an msdos signature
/dev/sde: unrecognized partition table type
Old situation:
No partitions found
New situation:
Units = sectors of 512 bytes, counting from 0
Device Boot Start End #sectors Id System
/dev/sde1 63 16771859 16771797 83 Linux
/dev/sde2 0 - 0 0 Empty
/dev/sde3 0 - 0 0 Empty
/dev/sde4 0 - 0 0 Empty
Warning: no primary partition is marked bootable (active)
This does not matter for LILO, but the DOS MBR will not boot this disk.
Successfully wrote the new partition table
Re-reading the partition table ...
If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)
to zero the first 512 bytes: dd if=/dev/zero of=/dev/foo7 bs=512 count=1
(See fdisk(8).)
fz-vm:~# sfdisk -d /dev/sda|sfdisk /dev/sdf
Checking that no-one is using this disk right now ...
OK
Disk /dev/sdf: 1044 cylinders, 255 heads, 63 sectors/track
sfdisk: ERROR: sector 0 does not have an msdos signature
/dev/sdf: unrecognized partition table type
Old situation:
No partitions found
New situation:
Units = sectors of 512 bytes, counting from 0
Device Boot Start End #sectors Id System
/dev/sdf1 63 16771859 16771797 83 Linux
/dev/sdf2 0 - 0 0 Empty
/dev/sdf3 0 - 0 0 Empty
/dev/sdf4 0 - 0 0 Empty
Warning: no primary partition is marked bootable (active)
This does not matter for LILO, but the DOS MBR will not boot this disk.
Successfully wrote the new partition table
Re-reading the partition table ...
If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)
to zero the first 512 bytes: dd if=/dev/zero of=/dev/foo7 bs=512 count=1
(See fdisk(8).)
fz-vm:~# mdadm -C -l10 -n4 /dev/md0 /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1
mdadm: array /dev/md0 started.
fz-vm:~# cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath]
md0 : active raid10 sdf1[3] sde1[2] sdd1[1] sdc1[0]
16771584 blocks 64K chunks 2 near-copies [4/4] [UUUU]
[====>................] resync = 24.9% (4181248/16771584) finish=2.6min speed=77772K/sec
unused devices: <none>
fz-vm:~# cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath]
md0 : active raid10 sdf1[3] sde1[2] sdd1[1] sdc1[0]
16771584 blocks 64K chunks 2 near-copies [4/4] [UUUU]
[===========>.........] resync = 56.4% (9472896/16771584) finish=1.5min speed=78378K/sec
unused devices: <none>
fz-vm:~# cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath]
md0 : active raid10 sdf1[3] sde1[2] sdd1[1] sdc1[0]
16771584 blocks 64K chunks 2 near-copies [4/4] [UUUU]
[==================>..] resync = 92.8% (15571968/16771584) finish=0.2min speed=80976K/sec
unused devices: <none>
fz-vm:~# cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath]
md0 : active raid10 sdf1[3] sde1[2] sdd1[1] sdc1[0]
16771584 blocks 64K chunks 2 near-copies [4/4] [UUUU]
unused devices: <none>
fz-vm:~# mdadm -f /dev/md0 /dev/sdc1
mdadm: set /dev/sdc1 faulty in /dev/md0
fz-vm:~# mdadm -r /dev/md0 /dev/sdc1
mdadm: hot removed /dev/sdc1
fz-vm:~# mdadm -a /dev/md0 /dev/sdc1
mdadm: re-added /dev/sdc1
fz-vm:~# mdadm -f /dev/md0 /dev/sdd1
mdadm: set /dev/sdd1 faulty in /dev/md0
fz-vm:~# mdadm -r /dev/md0 /dev/sdd1
mdadm: hot removed /dev/sdd1
fz-vm:~# mdadm -a /dev/md0 /dev/sdd1
mdadm: re-added /dev/sdd1
fz-vm:~# mdadm -f /dev/md0 /dev/sde1
mdadm: set /dev/sde1 faulty in /dev/md0
fz-vm:~# mdadm -r /dev/md0 /dev/sde1
mdadm: hot removed /dev/sde1
fz-vm:~# mdadm -a /dev/md0 /dev/sde1
mdadm: re-added /dev/sde1
fz-vm:~# mdadm -Q --detail /dev/md0
/dev/md0:
Version : 00.90
Creation Time : Tue Aug 19 15:43:59 2008
Raid Level : raid10
Array Size : 16771584 (15.99 GiB 17.17 GB)
Used Dev Size : 8385792 (8.00 GiB 8.59 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Tue Aug 19 15:51:26 2008
State : clean, degraded
Active Devices : 1
Working Devices : 4
Failed Devices : 0
Spare Devices : 3
Layout : near=2, far=1
Chunk Size : 64K
UUID : 062f49a6:4e37e729:89ccbef7:ff5abfb0 (local to host fz-vm)
Events : 0.34
Number Major Minor RaidDevice State
0 0 0 0 removed
1 0 0 1 removed
2 0 0 2 removed
3 8 81 3 active sync /dev/sdf1
4 8 65 - spare /dev/sde1
5 8 49 - spare /dev/sdd1
6 8 33 - spare /dev/sdc1
fz-vm:~# cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath]
md0 : active raid10 sde1[4](S) sdd1[5](S) sdc1[6](S) sdf1[3]
16771584 blocks 64K chunks 2 near-copies [4/1] [___U]
unused devices: <none>
fz-vm:~# mdadm -A --update=resync /dev/md0
mdadm: /dev/md0 not identified in config file.
fz-vm:~# mdadm -A --update=resync /dev/md0 /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1
mdadm: device /dev/md0 already active - cannot assemble it
fz-vm:~# mdadm --grow -l10 -n4 /dev/md0
mdadm: raid10 array /dev/md0 cannot be reshaped.
fz-vm:~# mdadm -S /dev/md0
mdadm: stopped /dev/md0
fz-vm:~# mdadm -R /dev/md0
mdadm: failed to run array /dev/md0: Invalid argument
fz-vm:~# mdadm -A --update=resync /dev/md0 /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1
mdadm: /dev/md0 assembled from 1 drive and 3 spares - not enough to start the array.
fz-vm:~# cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath]
md0 : inactive sdf1[3](S) sdc1[6](S) sdd1[5](S) sde1[4](S)
33543168 blocks
unused devices: <none>
fz-vm:~# mdadm -Q --detail /dev/md0
mdadm: md device /dev/md0 does not appear to be active.
fz-vm:~# logout
Connection to fz-vm closed.
[EMAIL PROTECTED]:~$
