device-mapper & bd_claim

device-mapper & bd_claim

[Martin Waitz]

[-- Attachment #1: Type: text/plain, Size: 1031 bytes --]

hi :)

i use evms to mount some filesystems.
the root filesystem is located on /dev/hda1, all other partitions
are managed by evms.

this works without problems in 2.4.
however, evms refuses to create the logical volumes in 2.6.

the problem seems to be the addition of bd_claim in 2.6:
upon mounting the root filesystem, hda1 is claimed by the filesystem.
thus, hda is claimed by the bd_claim code, too.
evms tries to setup dm-tables using hda and fails to claim the device

so, how should this be solved?
i think it should be allowed to mix evms and 'normal' partitions on
the same device.

do we need to introduce claimed_region of the toplevel device instead
of claiming individual devices?

-- 
CU,		  / Friedrich-Alexander University Erlangen, Germany
Martin Waitz	//  Department of Computer Science 3       _________
______________/// - - - - - - - - - - - - - - - - - - - - ///
dies ist eine manuell generierte mail, sie beinhaltet    //
tippfehler und ist auch ohne grossbuchstaben gueltig.   /

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [Evms-devel] device-mapper & bd_claim

[Kevin Corry]

On Friday 24 October 2003 06:56, Martin Waitz wrote:
> hi :)
>
> i use evms to mount some filesystems.
> the root filesystem is located on /dev/hda1, all other partitions
> are managed by evms.
>
> this works without problems in 2.4.
> however, evms refuses to create the logical volumes in 2.6.
>
> the problem seems to be the addition of bd_claim in 2.6:
> upon mounting the root filesystem, hda1 is claimed by the filesystem.
> thus, hda is claimed by the bd_claim code, too.
> evms tries to setup dm-tables using hda and fails to claim the device
>
> so, how should this be solved?
> i think it should be allowed to mix evms and 'normal' partitions on
> the same device.
>
> do we need to introduce claimed_region of the toplevel device instead
> of claiming individual devices?

Please see the notes at the top of:
http://evms.sourceforge.net/patches/2.1.1/kernel/2.6.0-test8/bd_claim.patch

In general, if you want to "mix" users of a device, you'll just need to revert 
that patch. But this isn't the preferred solution. If you're using EVMS, 
ideally you should switch to using EVMS for all your volumes and partitions. 
Getting your root filesystem mounted through EVMS isn't terribly difficult, 
and you can find more details about it at:
http://evms.sourceforge.net/install/root.html

-- 
Kevin Corry
kevcorry@us.ibm.com
http://evms.sourceforge.net/

Re: [Evms-devel] device-mapper & bd_claim

[Don Mulvey]

>the problem seems to be the addition of bd_claim in 2.6:
>upon mounting the root filesystem, hda1 is claimed by the filesystem.
>thus, hda is claimed by the bd_claim code, too.
>evms tries to setup dm-tables using hda and fails to claim the device

I just saw this last night with 2.6.test6. Haven't had a chance to look at
it though. Couldn't activate compatibility vols on hda. Evms vols were
fine.

-Don