* dm-mon fails to load raid1 target
@ 2005-01-30 17:20 Molle Bestefich
2005-01-31 13:47 ` Kevin Corry
0 siblings, 1 reply; 3+ messages in thread
From: Molle Bestefich @ 2005-01-30 17:20 UTC (permalink / raw)
To: dm-devel; +Cc: gerte
Hi
I can't get dm_mon to load the raid1 target.
The syslog says (timestamps removed):
livecd device-mapper: : unknown target type
livecd
livecd device-mapper: error adding target to table
Seems that there's a completely blank syslog message (reproducible),
and a surplus colon in the first message. Might be related to the
dmraid tool. Anyway.
I'm booting with a Gentoo CD [gen2dmraid 0.99 - kernel: 2.6.9, driver
4.1.0, library 1.00.17-ioctl].
The /lib/modules/.../raid1.ko file is present.
I tried modprobe raid1 (fine), this didn't add the mirror target to
"dmsetup targets".
Tried unloading dm-mon, reloading raid1, loading dm-mon, still no mirror target.
Any hints on what is going wrong / what I am doing wrong?
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: dm-mon fails to load raid1 target
2005-01-30 17:20 dm-mon fails to load raid1 target Molle Bestefich
@ 2005-01-31 13:47 ` Kevin Corry
2005-02-01 8:41 ` Molle Bestefich
0 siblings, 1 reply; 3+ messages in thread
From: Kevin Corry @ 2005-01-31 13:47 UTC (permalink / raw)
To: dm-devel, Molle Bestefich; +Cc: gerte
On Sunday 30 January 2005 11:20 am, Molle Bestefich wrote:
> Hi
>
> I can't get dm_mon to load the raid1 target.
Do you mean "dm_mod", which is the core of the DM driver?
> The syslog says (timestamps removed):
> livecd device-mapper: : unknown target type
> livecd
> livecd device-mapper: error adding target to table
This means a user-space program tried to load a device-table for a target-type
that doesn't exist or couldn't be loaded.
> Seems that there's a completely blank syslog message (reproducible),
> and a surplus colon in the first message. Might be related to the
> dmraid tool. Anyway.
>
> I'm booting with a Gentoo CD [gen2dmraid 0.99 - kernel: 2.6.9, driver
> 4.1.0, library 1.00.17-ioctl].
>
> The /lib/modules/.../raid1.ko file is present.
That is the module for MD/Software-RAID RAID-1, not the Device-Mapper
mirroring module. They are completely different drivers that just happen to
be in the same directory in the kernel source and module trees.
> I tried modprobe raid1 (fine), this didn't add the mirror target to
> "dmsetup targets".
> Tried unloading dm-mon, reloading raid1, loading dm-mon, still no mirror
> target.
>
> Any hints on what is going wrong / what I am doing wrong?
The Device-Mapper mirroring target is called "dm-mirror". Check your kernel
configuration and make sure you have CONFIG_DM_MIRROR set to "y" or "m". If
necessary, you may need to rebuild your kernel to enable it. Once it's
enabled, run "dmsetup targets" and look for a "mirror" entry. If you've
compiled DM mirroring as a module, try "modprobe dm-mirror", and then run
"dmsetup targets" again.
--
Kevin Corry
kevcorry@us.ibm.com
http://evms.sourceforge.net/
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: dm-mon fails to load raid1 target
2005-01-31 13:47 ` Kevin Corry
@ 2005-02-01 8:41 ` Molle Bestefich
0 siblings, 0 replies; 3+ messages in thread
From: Molle Bestefich @ 2005-02-01 8:41 UTC (permalink / raw)
To: dm-devel; +Cc: gerte
Kevin Corry wrote:
> Molle Bestefich wrote:
>> I can't get dm_mon to load the raid1 target.
>
> Do you mean "dm_mod", which is the core of the DM driver?
Yes :-).
>> The syslog says (timestamps removed):
>> [...]
>
> This means a user-space program tried to load a device-table for a target-type
> that doesn't exist or couldn't be loaded.
>
>> I'm booting with a Gentoo CD [gen2dmraid 0.99 - kernel: 2.6.9, driver
>> 4.1.0, library 1.00.17-ioctl].
>>
>> The /lib/modules/.../raid1.ko file is present.
>
> That is the module for MD/Software-RAID RAID-1, not the Device-Mapper
> mirroring module. They are completely different drivers that just happen to
> be in the same directory in the kernel source and module trees.
Ack. Thank you for clearing that up.
I've never been able to install a working copy of Linux on my PC, so I
don't know squat.
Linux cannot use the disks on my ATARAID controller, even though it
says on the box that the controller supports Linux. Using the
proprietary driver, I can't recompile the kernel with eg. appropriate
sound card drivers and the open source ATARAID driver isn't up-to-date
with the metadata format.
I'm trying again now that DM and DMRAID has arrived, but (as is
probably apparent), I haven't got a clue what I'm doing :-)
>> Any hints on what is going wrong / what I am doing wrong?
>
> The Device-Mapper mirroring target is called "dm-mirror". Check your kernel
> configuration and make sure you have CONFIG_DM_MIRROR set to "y" or "m". If
> necessary, you may need to rebuild your kernel to enable it. Once it's
> enabled, run "dmsetup targets" and look for a "mirror" entry. If you've
> compiled DM mirroring as a module, try "modprobe dm-mirror", and then run
> "dmsetup targets" again.
Gerte, is there somehow that I can persuade you to build a new LiveCD
with dm-mirror support?
I would like to do it myself, but am a bit stuck since no Linux distro
will install on my PC :-/..
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-02-01 8:41 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-01-30 17:20 dm-mon fails to load raid1 target Molle Bestefich
2005-01-31 13:47 ` Kevin Corry
2005-02-01 8:41 ` Molle Bestefich
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.