Re: multiple arrays and unmapped partitions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, May 01, 2008 at 12:16:43AM +0200, Lucas B. Cohen wrote:
> > Sent: mardi 29 avril 2008 11:07
> > 
> > Hi Lucas,
> > 
> > kpartx workaround works for you or not ?
> 
> Hello Heinz, thanks for reading,
> 
> kpartx works as well as the "dmraid -an isw_di && dmraid -ay isw_di" kludge
> I mentioned. Is there an easier way than manually adding a call to either
> one of them in the initrd scripts (my root partition is not being mapped)

Depends on the distro I think.
Fedora/RHEL automatically runs kpartx on sets discovered by dmraid.

> 
> > In order to be able to test this further, I'd need the partition
> > table sector(s) in addition to the "dmraid -rD" output you provided.
> 
> You can find them at http://elmo.xzibition.com/~lbc/parttables.tar.gz

Ok, will look into it.

Heinz

> 
> 
> Lucas
> 
> > Cheers,
> > Heinz
> 
> > 
> > On Sun, Apr 27, 2008 at 03:44:16PM +0200, Lucas B. Cohen wrote:
> > > Hi,
> > >
> > > Have there been significant changes or advances regarding the issue of
> > > partitions not being mapped when more than one array is present in a
> > system,
> > > since Liviu Balan's message on the subject [1] last year?
> > >
> > > With rc13 and rc14, depending on kernel version, either the first
> > (2.6.18)
> > > or second array (2.6.22 and up) get "missed" in my system (Intel
> > Software
> > > Raid on Intel P35 with ICH9R).
> > >
> > > Aside from Heinz's reply to [1] (suggesting a kpartx-based workaround),
> > I've
> > > noticed that deactivating the non-mapped array *only* before activating
> > it
> > > allows the missing nodes to be created in /dev/mapper. (Something like
> > > dmraid -an isw_di && dmraid -ay isw_di)
> > >
> > > I imagine the "use kpartx instead of my own DOS metadata format handler"
> > > item in rc14's TODO is relevant to this.
> > >
> > > In case it can be of use, the output of "dmraid -rD" for my system is
> > > accessible at [2].
> > >
> > > Any insight is appreciated, as I'm having a hard time finding relevant
> > > information on this problem elsewhere.
> > >
> > > Regards,
> > >
> > > Lucas Cohen
> > >
> > >
> > > [1] http://www.redhat.com/archives/ataraid-list/2007-April/msg00009.html
> > > [2] http://elmo.xzibition.com/~lbc/dmraid-metadata.tar.gz
> > >
> > > _______________________________________________
> > > Ataraid-list mailing list
> > > Ataraid-list@xxxxxxxxxx
> > > https://www.redhat.com/mailman/listinfo/ataraid-list
> > 
> > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> > =-=-
> > 
> > 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
> 
> _______________________________________________
> Ataraid-list mailing list
> Ataraid-list@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/ataraid-list

_______________________________________________
Ataraid-list mailing list
Ataraid-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/ataraid-list

[Index of Archives]     [Linux RAID]     [Linux Device Mapper]     [Linux IDE]     [Linux SCSI]     [Kernel]     [Linux Books]     [Linux Admin]     [GFS]     [RPM]     [Yosemite Campgrounds]     [AMD 64]

  Powered by Linux