close 705454
thanks
Hi Daniel,
>your problem doesn't affect arrays with superblock 1.x and superblock
>0.9 is really not much used anymore.. do you still have the issue?
as far as I can tell, all RAIDs I have are using metadata=1.2 by now.
>I don't think this has much traction to get ever
tag 705454 + moreinfo
thanks
Hi Thorsten,
your problem doesn't affect arrays with superblock 1.x and superblock
0.9 is really not much used anymore.. do you still have the issue?
I don't think this has much traction to get ever fixed upstream and
suggest to close the bug. What do you think?
On Wed, 1 May 2013, NeilBrown wrote:
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.
Doubtful…
What does mdadm --examine --scan -v show? It should list
On Mon, 6 May 2013 09:22:42 +0200 (CEST) Thorsten Glaser t.gla...@tarent.de
wrote:
On Wed, 1 May 2013, NeilBrown wrote:
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
On Mon, 6 May 2013, NeilBrown wrote:
It appears that your '2' partitions are at an offset of a multiple of 64K
Well of course they are ☺
Both sda and sda2 look like they have the same superblock, because the
superblock is at the end of both. This can seriously confuse mdadm. It
would
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
On Tue, 30 Apr 2013 15:42:34 +0200 (CEST) Thorsten Glaser
t.gla...@tarent.de 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
7 matches
Mail list logo
