Favor md volumes over raw devices when present
Bug #1498930 reported by
Nate House
This bug report is a duplicate of:
Bug #1491148: growpart doesn't work with mdraid devices.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| cloud-utils |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
Up until v1.1 of mdadm, metadata was stored at the end of the disk and is reflected by the usable volume space on the raid volume compared to the source disks sizes. With the metadata being stored at the end and growpart resizing the source disk on initial boot, it appears to cause the raid volumes filesystem to become corrupt.
There could be alot of other factors at play and using raid for cloud boot volumes might not be a common use case. Seems like setting raid volume prescedence over raw disks shouldn't be difficult to detect and implement though.
| Changed in cloud-utils: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
Revision history for this message
| Scott Moser (smoser) wrote | #1 |
To post a comment you must log in.
Hi,
I'm going to mark this as a dupe of bug 1491148 growpart doesn't work with mdraid devices.
If you think otherwise, feel free to re-open.
How old is mdadm 1.1 ? As best i can tell , version 3.0 was released in 2009. Is v1.1 a *metadata* version?