|
Hi Heinz, Well, actually I'm not getting 2 different devices. In the example I've reported, each time I reboot I get just a single device, but its name changes. As stated in last e-mail: 1st boot: /dev/mapper/ddf1_4c53492020202020808627c300000000346e1b3c00000a28 2nd boot: /dev/mapper/ddf1_4c53492020202020808627c300000000346e1f3100000a28 3rd boot: /dev/mapper/ddf1_4c53492020202020808627c300000000346e1ff400000a28 I've sent you the image on the last boot (3rd), so you're having device name ddf1_...e1ff400000a28. So the problem is that device name get changing each reboot, while I don't have any other RAID chain in the system. Regards, Nhan Heinz Mauelshagen wrote: Hi Nhan, I get the following results with your metadata sample (/dev/dm-29, /dev/dm-33 being sparse devices in my testbed with your metadata on): # dmraid -r /dev/dm-29: ddf1, ".ddf1_disks", GROUP, ok, 486326272 sectors, data@ 0 /dev/dm-33: ddf1, ".ddf1_disks", GROUP, ok, 486326272 sectors, data@ 0 # dmraid -tay ddf1_4c53492020202020808627c300000000346e1ff400000a28: 0 486326272 mirror core 2 131072 nosync 2 /dev/dm-29 0 /dev/dm-33 0 After activation: # dmraid -s *** Group superset .ddf1_disks --> Active Subset name : ddf1_4c53492020202020808627c300000000346e1ff400000a28 size : 486326272 stride : 128 type : mirror status : ok subsets: 0 devs : 2 spares : 0 The only device created is: brw-rw---- 1 root disk 253, 34 19. Nov 11:22 /dev/mapper/ddf1_4c53492020202020808627c300000000346e1ff400000a28 This all looks fine. I wonder, if you have another drive with DDF metadata on causing the 2 /dev/mapper/ devices ? Ragards, Heinz On Thu, Nov 15, 2007 at 09:52:22PM +0100, Nhan NGO DINH wrote: -- Nhan NGO DINH Dilogix S.r.l. Tel: +39 06 85304201 Fax: +39 06 85800436 Cel: +39 328 4711229 e-mail: nhan.ngodinh@xxxxxxxxxx web: http://www.dilogix.it See legal notes: http://www.dilogix.it/legal_mail.html |
_______________________________________________ Ataraid-list mailing list Ataraid-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/ataraid-list
