Re: freshly grown array shrinks after first reboot - major data loss

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



John Robinson wrote:
On 02/09/2011 10:19, Pim Zandbergen wrote:
On 09/01/2011 09:41 PM, Doug Ledford wrote:
I could file a bug on bugzilla.redhat.com if that would help.

Feel free, it helps me track things.

https://bugzilla.redhat.com/show_bug.cgi?id=735306

I'm not sure whether it's just the --grow that should complain, or perhaps the earlier step of
  mdadm /dev/md/array-using-0.90-metadata --add /dev/3TB
should also complain (even if it'll work with less than 2TiB in use, it ought to tell the user they won't be able to grow the array).

Perhaps Neil can confirm, but the limitation seems to be using 2TB as an array member size, I am reasonably sure that if you had partitioned the drives into two 1.5TB partitions you could have created the array just fine.

Note that this is just a speculation, not a suggestion to allow using 0.90 metadata, and I do realize that this array was created in the dark ages, not being created new.

--
Bill Davidsen<davidsen@xxxxxxx>
  We are not out of the woods yet, but we know the direction and have
taken the first step. The steps are many, but finite in number, and if
we persevere we will reach our destination.  -me, 2010



--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux