On Sat, Aug 30, 2008 at 11:54:45AM +0200, Frans Pop wrote:
> On Saturday 30 August 2008, Giuseppe Iuculano wrote:
> > Comments/Problems:
> > I used a set of fakeraid qcow2 format disk images
> > (http://www.themuso.id.au/ubuntu/dmraid-empty-disks.tar.bz2), but boot
> > loader installation failed.
> > It seems that installer recognize /dev/mapper/* as an lvm volume, and
> > so disable grub installation.
>
> That should not happen. There is an exception for dmraid devices, which
> apparently no longer works.
>
> From the output you provide the reason seems to be that partitions are now
> created as <dmraid dev>p<partition nr>. The problem is the "p" between
> the device and the partition number which AFAICT did not use to be there
> before.
This is coming from libparted. The following patch gives us back the
previous naming:
--- parted-1.8.8.git.2008.03.24/libparted/arch/linux.c
+++ parted-1.8.8.git.2008.03.24/libparted/arch/linux.c
@@ -2038,9 +2038,6 @@
} else if (dev->type == PED_DEVICE_DAC960
|| dev->type == PED_DEVICE_CPQARRAY
|| dev->type == PED_DEVICE_ATARAID
-#ifdef ENABLE_DEVICE_MAPPER
- || dev->type == PED_DEVICE_DM
-#endif
|| isdigit (dev->path[path_len - 1]))
snprintf (result, result_len, "%sp%d", dev->path, num);
else
But this is not enough to fix the issue. Same OOM happens later on.
I am not sure that I completely understand the way dmraid support is
supposed to create the partitions on disk. As far as I can read in
parted 1.8 source, asking libparted to create a new partition on a
dm device will simply create a "linear" mapping on top of the existing
device. It will not result in changes in the underlying disk
partitions.
Looks like dmraid was not tested during the switch to libparted 1.8.
Thanks to the empty images pointed by Guiseppe, it is pretty easy to do
so, but I am afraid that the changes needed might be quite invasive.
Cheers,
--
Jérémy Bobbio .''`.
lunar@debian.org : :Ⓐ : # apt-get install anarchism
`. `'`
`-
Attachment:
signature.asc
Description: Digital signature