[Bug 1074606] [NEW] gparted identifying incorrect raid arrays

[Launchpad Bug Tracker]

You have been subscribed to a public bug by Phillip Susi (psusi):

SRU Justification:

Users get a popup reporting internal errors/bugs relating to oddly named
raid arrays that do not exist.  There was a module that probed for mdadm
devices by running mdadm --examine --scan to scan all disks for raid
metadata.  This is incorrect and sometimes reports incorrect information
so this module was removed, and gparted now relies on /proc/partitions
to detect active raid arrays.  There should be little to no chance of
regression.

I realize that normally SRU bug fixes should be deployed to the
development version first, but since raring is still running the same
version which is synced to debian, I would rather just wait until I
upload the new upstream release that contains this fix in a few days,
which will then be synced to raring.

End SRU justification.

On startup, gparted complains with several popups that it has an
internal parted bug trying to stat /dev/md/XXXX.  This appears to be
caused by its reliance on running mdadm --examine --scan to identify
raid arrays.  Recent versions of mdadm now report the existence of
"containers" that are not usable block devices, but gparted thinks they
are.  It also reports the preferred major number rather than the actual.
In other words, if the metadata says it is supposed to be /dev/md0, that
is what mdadm reports, however it may have been activated as /dev/md127
instead, causing gparted to try to use a device that does not exist.

** Affects: gparted
     Importance: Medium
         Status: Confirmed

** Affects: gparted (Ubuntu)
     Importance: Medium
     Assignee: Phillip Susi (psusi)
         Status: In Progress

** Affects: gparted (Ubuntu Quantal)
     Importance: High
     Assignee: Phillip Susi (psusi)
         Status: In Progress

-- 
gparted identifying incorrect raid arrays
https://bugs.launchpad.net/bugs/1074606
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.