Public bug reported:
Binary package hint: mdadm
It is possible to command mdadm to grow an array such that the array space on a
component partition exceeds the maximum size writeable in metadata 0.90 format,
which is just over 2TB (4 bytes representing sector size). When told to do
this, mdadm appears to do it without error and writes a bogus sector count into
the 4 byte container in the super-blocks. Now the system operates with the
over-enlarged array without apparent issue but only until the next reboot when
the system is told the array size based on the superblock value. User data
becomes inaccessible/LVMs don't mount with seemingly no way to recover the
inaccessible data.
Obviously, mdadm should refuse to grow the array size beyond the size
restriction of its own metadata.
Seen using mdadm - v2.6.7.1 - 15th October 2008 and Ubuntu server 10.04 64-bit
** Affects: mdadm (Ubuntu)
Importance: Undecided
Status: New
** Tags: mdadm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/794963
Title:
madam allows growing an array beyond metadata size limitations
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/794963/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
