libparted hides fakeraid raid10 disks

Bug #311179 reported by Theo Snelleman
46
This bug affects 6 people
Affects Status Importance Assigned to Milestone
parted (Ubuntu)
Fix Released
Medium
Phillip Susi

Bug Description

Binary package hint: libparted1.8-9

I've installed ubuntu 8.10 on a fakeraid raid10-set.

I booted using the live-cd and then installed dmraid manually
My raid-set was detected correctly and showed up in /dev/mapper.

Then I started ubiquity, but the installer did not show my read10-device. He did show me the 2 raid0-set that are part of the raid10-set. ubiquity is using parted_devices and parted_devices is using libparted.

When I run parted_devices manually I get the following results:
/dev/sda 500107862016 ATA ST3500320AS
/dev/sdb 500107862016 ATA ST3500320AS
/dev/sdc 500107862016 ATA ST3500320AS
/dev/sdd 500107862016 ATA ST3500320AS
/dev/mapper/isw_bfgggbebhf_diskset-0 1000210694144 Linux device-mapper
/dev/mapper/isw_bfgggbebhf_diskset-1 1000210694144 Linux device-mapper

I would expect the following result:
/dev/mapper/isw_bfgggbebhf_diskset 1000210694144 Linux device-mapper

It looks like that the patch parted-dmraid.dpatch in libparted is causing the problems. I removed this patch, build and installed libparted and then my raid10-device showed up.

I think that the new function _is_dmraid_major is not correct. isw_bfgggbebhf_diskset is the slave of my partitions, but still is the major device.

output of /dev/mapper:
crw-rw---- 1 root root 10, 60 2008-12-24 11:04 control
brw-rw---- 1 root disk 254, 0 2008-12-24 11:04 isw_bfgggbebhf_diskset
brw-rw---- 1 root disk 254, 2 2008-12-24 11:04 isw_bfgggbebhf_diskset-0
brw-rw---- 1 root disk 254, 3 2008-12-24 11:04 isw_bfgggbebhf_diskset1
brw-rw---- 1 root disk 254, 1 2008-12-24 11:04 isw_bfgggbebhf_diskset-1
brw-rw---- 1 root disk 254, 4 2008-12-24 11:04 isw_bfgggbebhf_diskset3
brw-rw---- 1 root disk 254, 6 2008-12-24 11:04 isw_bfgggbebhf_diskset5
brw-rw---- 1 root disk 254, 7 2008-12-24 11:04 isw_bfgggbebhf_diskset6

contents of /sys/block/dm*/slaves/
dm-0/slaves/:
dm-1 dm-2

dm-1/slaves/:
sdb sdd

dm-2/slaves/:
sda sdc

dm-3/slaves/:
dm-0

dm-4/slaves/:
dm-0

dm-6/slaves/:
dm-0

dm-7/slaves/:
dm-0

version of libparted: 1.8.8.git.2008.03.24-7ubuntu7

regards,
Theo

Related branches

Revision history for this message
Luke Yelavich (themuso) wrote :

If possible, could you try with jaunty and tell me if you get the same behavior? I remember testing dmraid with ubiquity in jaunty, and the RAID array showed up correctly. I'll try with intrepid next week to see if I can reproduce your problem.

Revision history for this message
Theo Snelleman (theo-snelleman) wrote :

hi Luke,

thank you for spending some time on this bug.

I just tried Jaunty, but unfortunately I get the same behaviour.
After disabling the patch "patch-dmraid" in libparted, everything worked again as expected.

regards,
Theo

Revision history for this message
allxk (allxk) wrote :

Installing Ubuntu 10.10 64-bit
Please see attached image:
The disk partitioned with gparted.
Ubuntu 10.10 x64 Installation window will not show any partitions, and edit partition option.
Same thing with Ubuntu 10.10 x32.

Revision history for this message
ctr (ctr) wrote :

I'm having the same problem with Natty alpha1 (x64), not sure if libparted or Ubiquity is causing this...

Revision history for this message
gregdavisfromnj (gregdavis) wrote :

I tried installing onto a nested fakedraid and since 9.10, have never gotten it to install. This bug seems to be the problem, and removing the patch as described here got me close to complete. The Grub2 didn't seem to like the nested fakeraid, at that point. Anyway trying just now with 11.04, dmraid doesn't seem active when the installer is run straight from boot. When you have the option to try or install, click "try" to start the livecd, and use a terminal to execute "sudo dmraid -ay", which will start the device mapper. Then you can click the shortcut on the desktop folder to install, and the RAID partitions will be there. Whether or not this bug bites you then, is another question.

Revision history for this message
Phillip Susi (psusi) wrote :

This is a bug in dmraid.patch. It identifies the raid10 as a partition because its dependencies are also device-mapper devices, and so excludes it. I have an idea on how to fix this.

Changed in parted (Ubuntu):
assignee: nobody → Phillip Susi (psusi)
importance: Undecided → Medium
status: New → In Progress
summary: - libparted does not return the correct devices to ubiquity
+ libparted hides fakeraid raid10 disks
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package parted - 2.3-8ubuntu2

---------------
parted (2.3-8ubuntu2) precise; urgency=low

  * Add 16-dos-partitions.patch: Fix parted to correctly handle
    more than 16 partitions on dos partition tables.
  * Add dm-part-sync.patch: Backport fix to allow modifying partitions
    on dmraid disks while other partitions are in use.
  * Replace dmraid.patch: Reimplemented and forwarded upstream,
    allows dmraid raid10 disks to show up (LP: #311179)
  * Replace loop-partitions.patch: this patch used to make sure that
    we don't try to partition loop devices. Now it backports a few
    upstream changes to allow partitioning loop devices since that is
    supported on Linux since 3.0. It includes a change that also fixes
    support for > 16 partitions.
  * Add skip-floppy.patch: don't probe floppy drives. (LP: #910379)
 -- Phillip Susi <email address hidden> Sat, 03 Dec 2011 09:50:05 -0500

Changed in parted (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.