Bug 15665

Summary:	add support for partitionable RAIDs (eg: /dev/md_d0p2 & /dev/md0p2)
Product:	Mageia	Reporter:	Thierry Vignaud <thierry.vignaud>
Component:	RPM Packages	Assignee:	Mageia tools maintainers <mageiatools>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	High	CC:	marja11, pterjan, tmb
Version:	Cauldron
Target Milestone:	Mageia 7
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	drakx-installer-stage2	CVE:
Status comment:
Bug Depends on:
Bug Blocks:	15791

Description Thierry Vignaud 2015-04-09 15:22:14 CEST

Since 2.6.x kernels[1], a new type of MD device was introduced, a partitionable array:
- device names is: md -> md_d
- partitions: md_d0p2

Since kernel-2.6.28[2], regular arrays can be partitioned too, eg: /dev/md/md0p2.

We should add support for both in diskdrake.

Then we could show such partitioned RAIDs in the partitioning wizard (bug #5800)...


[1] http://git.kernel.org/cgit/linux/kernel/git/tglx/history.git/log/drivers/md/md.c?qt=grep&q=partition
http://git.kernel.org/cgit/linux/kernel/git/tglx/history.git/commit/drivers/md/md.c?id=1797a796c7333ed02bfd8883bbaafaec867ddeb2

[2] http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/md?id=92850bbd71

Reproducible: 

Steps to Reproduce:

Thierry Vignaud 2015-04-09 15:22:23 CEST

CC: (none) => pterjan

Comment 1 Thomas Backlund 2015-04-09 17:10:55 CEST

This would help for mdadm managed isw_ raids too as the fakeraid disk is 

/dev/md126

and partitions on it:

/dev/md126p1
/dev/md126p2

and so on...

CC: (none) => tmb

Thierry Vignaud 2015-04-10 08:57:08 CEST

Summary: add support for partitionable RAIDs => add support for partitionable RAIDs (eg: /dev/md_d0p2 & /dev/md0p2)

Thierry Vignaud 2015-04-29 08:59:17 CEST

Blocks: (none) => 15791

Comment 2 Thierry Vignaud 2015-05-22 14:12:47 CEST

Example: see attachment #6612 [details]:
* error: failed to add partition #4 on /dev/mapper/isw_baecbdbe_Sys at /usr/lib/libDrakX/partition_table/gpt.pm line 154.

Samuel Verschelde 2015-06-06 16:26:35 CEST

Target Milestone: --- => Mageia 6

Marja Van Waes 2016-07-21 15:24:30 CEST

CC: (none) => marja11
Assignee: bugsquad => pterjan

Comment 3 Samuel Verschelde 2016-10-10 22:01:12 CEST

Pascal (or other members of the Mageia Tools maintainer group), this bug report is currently targeted for Mageia 6. Is that something you can handle or should we postpone to Mageia 7?

CC: (none) => mageiatools

Samuel Verschelde 2016-10-10 22:01:27 CEST

Priority: Normal => High

Comment 4 Pascal Terjan 2016-10-10 22:26:34 CEST

I am not planning to work on that anytime soon.

A first step would be to update devices.pm (we probably want to change it to use /sys first and fallback on hardcoded stuff instead if the opposite).

Comment 5 Samuel Verschelde 2016-10-10 22:43:07 CEST

(In reply to Pascal Terjan from comment #4)
> I am not planning to work on that anytime soon.
> 
> A first step would be to update devices.pm (we probably want to change it to
> use /sys first and fallback on hardcoded stuff instead if the opposite).

Ok, I'll set the Milestone as Mageia 7 unless someone steps in rapidly.

CC: mageiatools => (none)
Assignee: pterjan => mageiatools
Target Milestone: Mageia 6 => Mageia 7

Comment 6 Aurelien Oudelet 2020-09-19 18:08:55 CEST

Hi,
This is High priority bug for a good reason.

Making Mageia even better than ever is best direction.
In order to do right thing, this bug should be examined and fixed as soon as possible.

Packagers, please make the status to Assigned when you are working on this.
Feel free to reassign the bug if bad-triaged. Also, if bug is old, please close it.

On October 1st 2020, we will drop priority to normal.