Mailinglist Archive: yast-devel (128 mails)

< Previous Next >
Re: [yast-devel] Problem with lvm on hardware raid
  • From: Christian Ehrlicher <Ch.Ehrlicher@xxxxxx>
  • Date: Fri, 19 Feb 2010 15:48:36 +0100
  • Message-id: <4B7EA4C4.9020309@xxxxxx>
Thomas Fehr schrieb:
On Wed, Feb 17, Arvin Schnell wrote:

On Wed, Feb 17, 2010 at 08:05:13PM +0100, Christian Ehrlicher wrote:

We've a similar problem like described in bug #231221 ( ). Yast can't create a
logical volume and fails with error -4017 (LVM_PV_STILL_ADDED)
--> /dev/block/104:3 needs a mapping to /dev/cciss/c0d0p3

It's correctly detected:
"dev_names":["/dev/cciss/c0d0", "/dev/block/104:0", "/dev/disk/by-
id/cciss-3600508b1001052395359305442350500", "/dev/disk/by-
path/pci-0000:06:00.0", "/dev/disk/by-id/edd-int13_dev80"]
I can provide the full y2log - but it's huge and therefore I decided to
append the error part.

When I'm correct I need to add an additional check for /dev/cciss in
Storage::findVolume() ( - is this correct?

The normal way is to add "/dev/block/104:3" to the alt_names of
the partition, e.g. in the constructor of Partition. Major and
Minor number should already be read in the Volume constructor.

If so - how can I add a modified libstorage to my install source (we're
doing a
network install)? We need to install 9 servers with this raid controller
our plan was to use autoyast for this...

You can make a new RPM of libstorage and add it as a driver
update (dud) in linuxrc, see

Attached patch should fix your problem.
We will have a more robust solution for next openSuSE but this should
do for now.

The patch did not apply to official source rpm for 11.2 therefore I
created an own patch as described in my other post. Thx for the help,


< Previous Next >