On Mon, Nov 19, 2007 at 05:03:04PM +0100, Nhan NGO DINH wrote:
> Hi Heinz,<br>
> Well, actually I'm not getting 2 different devices.<br>
> In the example I've reported, each time I reboot I get just a single
> device, but its name changes.<br>
> As stated in last e-mail:<br>
> 1st boot:
> /dev/mapper/ddf1_4c53492020202020808627c300000000346e1b3c00000a28<br>
> 2nd boot:
> /dev/mapper/ddf1_4c53492020202020808627c300000000346e1f3100000a28<br>
> 3rd boot:
> /dev/mapper/ddf1_4c53492020202020808627c300000000346e1ff400000a28<br>
> <br>
> I've sent you the image on the last boot (3rd), so you're having device
> name ddf1_...e1ff400000a28.<br>
> So the problem is that device name get changing each reboot, while I
> don't have any other RAID chain in the system.<br>
<SNIP>
Ah, I misinterpreted your issue :(
Well, it seems to look like the BIOS updating the DDF volumes name
and hence causing the mapped device name changes.
I gather this is bad for initrd and /etc/fstab name persistency.
There's 2 ways to work around this:
o use the DDF volume as an LVM physical volume, and create logical
volumes in it for OS installation, hence having persistent LV names.
Not sure if installers will fall on their back trying this
o leverage the initrd/initscripts to compensate for the name change
Regards,
Heinz -- The LVM Guy --
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Red Hat GmbH
Consulting Development Engineer Am Sonnenhang 11
Storage Development 56242 Marienrachdorf
Germany
Mauelshagen@xxxxxxxxxx PHONE +49 171 7803392
FAX +49 2626 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
_______________________________________________
Ataraid-list mailing list
Ataraid-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/ataraid-list
