[Bug 311179] Re: libparted hides fakeraid raid10 disks

[Launchpad Bug Tracker]

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 <psusi at ubuntu.com>   Sat, 03 Dec 2011 09:50:05 -0500

** Changed in: parted (Ubuntu)
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to parted in Ubuntu.
https://bugs.launchpad.net/bugs/311179

Title:
  libparted hides fakeraid raid10 disks

Status in “parted” package in Ubuntu:
  Fix Released

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/parted/+bug/311179/+subscriptions