On Tue, 30 Apr 2013 15:42:34 +0200 (CEST) Thorsten Glaser <[email protected]> wrote:
> reassign 705454 mdadm > found 705454 3.2.5-5 > retitle 705454 mdadm: --examine --scan generates wrong #spares > thanks > > I can reproduce this in a "live" sid system by creating > the md arrays then running this command: > > root@tglase:/ # mdadm --examine --scan > ARRAY /dev/md0 UUID=b4a6dcca:639ab49e:3cbfd189:3a086020 > spares=1 > ARRAY /dev/md1 UUID=b1518a63:e8fe3e9f:3cbfd189:3a086020 > spares=2 > root@tglase:/ # cat /proc/mdstat > Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] > [multipath] > md1 : active raid10 sdf2[4](S) sde2[3] sdd2[2] sdc2[1] sda2[0] > 975721472 blocks 512K chunks 2 near-copies [4/4] [UUUU] > > md0 : active raid1 sdf1[4](S) sde1[3] sdd1[2] sdc1[1] sda1[0] > 524224 blocks [4/4] [UUUU] > > unused devices: <none> "mdadm --examine --scan" looks at all devices, whether they are currently attached to an md array or not. Maybe it found a device that looked like a spare but isn't currently know to md. What does "mdadm --examine --scan -v" show? It should list "dev=...." for each array. Also you might be wanting 'mdadm --detail --scan' if you already have the arrays assembled. NeilBrown
signature.asc
Description: PGP signature
