I have a few questions about drbd.
1) I am doing investigations into building an HA environment using
Linux and have found drbd one solution for mirroring data between two Linux
machines. How stable is it to use in a semi-production environment (go-live
in April 2001)?
2) I am having trouble compiling drbd 0.5.7 on Redhat 6.2 using the
2.2.16-3 kernel. I have added -DCONFIG_MODVERSIONS and -DMODVERSIONS (did
not compile without it) to KERNFLAGS in Makefile.vars. I still get a message
from depmod -a saying "depmod: *** Unresolved symbols in
/lib/modules/2.2.16-3.1smp/block/drbd.o". Then when I try to insmod it, it
comes up with:
Using /lib/modules/2.2.16-3.1smp/block/drbd.o
/lib/modules/2.2.16-3.1smp/block/drbd.o: unresolved symbol
proc_unregister_Ra668f85e
/lib/modules/2.2.16-3.1smp/block/drbd.o: unresolved symbol
sock_alloc_R546a968e
/lib/modules/2.2.16-3.1smp/block/drbd.o: unresolved symbol
sock_sendmsg_Rd80b12e0
/lib/modules/2.2.16-3.1smp/block/drbd.o: unresolved symbol kernel_flag
/lib/modules/2.2.16-3.1smp/block/drbd.o: unresolved symbol
sock_create_R71055f51
/lib/modules/2.2.16-3.1smp/block/drbd.o: unresolved symbol
kernel_thread_R7e9ebb05
/lib/modules/2.2.16-3.1smp/block/drbd.o: unresolved symbol
proc_root_R9f91dbb5
/lib/modules/2.2.16-3.1smp/block/drbd.o: unresolved symbol
kill_proc_info_R84c0b0d1
/lib/modules/2.2.16-3.1smp/block/drbd.o: unresolved symbol
sock_release_R0fbed7c1
/lib/modules/2.2.16-3.1smp/block/drbd.o: unresolved symbol
sock_recvmsg_R935ddbd6
/lib/modules/2.2.16-3.1smp/block/drbd.o: unresolved symbol
proc_register_R8b411fd1
/lib/modules/2.2.16-3.1smp/block/drbd.o: unresolved symbol
send_sig_info_Rf910c6d7
Thanks in Advance
Richard Mottershead
Senior Systems Engineer
McKessonHBOC - Nottingham
----------------------------------------------------------------------------
The information contained in this e-mail is confidential and is intended
only for the named recipient(s). If you are not the intended recipient you
must not copy, distribute, or take any action or reliance on it.
If you have received this e-mail in error, please notify the sender.
Any unauthorised disclosure of the information contained in this e-mail
is strictly prohibited.
----------------------------------------------------------------------------
1) I am doing investigations into building an HA environment using
Linux and have found drbd one solution for mirroring data between two Linux
machines. How stable is it to use in a semi-production environment (go-live
in April 2001)?
2) I am having trouble compiling drbd 0.5.7 on Redhat 6.2 using the
2.2.16-3 kernel. I have added -DCONFIG_MODVERSIONS and -DMODVERSIONS (did
not compile without it) to KERNFLAGS in Makefile.vars. I still get a message
from depmod -a saying "depmod: *** Unresolved symbols in
/lib/modules/2.2.16-3.1smp/block/drbd.o". Then when I try to insmod it, it
comes up with:
Using /lib/modules/2.2.16-3.1smp/block/drbd.o
/lib/modules/2.2.16-3.1smp/block/drbd.o: unresolved symbol
proc_unregister_Ra668f85e
/lib/modules/2.2.16-3.1smp/block/drbd.o: unresolved symbol
sock_alloc_R546a968e
/lib/modules/2.2.16-3.1smp/block/drbd.o: unresolved symbol
sock_sendmsg_Rd80b12e0
/lib/modules/2.2.16-3.1smp/block/drbd.o: unresolved symbol kernel_flag
/lib/modules/2.2.16-3.1smp/block/drbd.o: unresolved symbol
sock_create_R71055f51
/lib/modules/2.2.16-3.1smp/block/drbd.o: unresolved symbol
kernel_thread_R7e9ebb05
/lib/modules/2.2.16-3.1smp/block/drbd.o: unresolved symbol
proc_root_R9f91dbb5
/lib/modules/2.2.16-3.1smp/block/drbd.o: unresolved symbol
kill_proc_info_R84c0b0d1
/lib/modules/2.2.16-3.1smp/block/drbd.o: unresolved symbol
sock_release_R0fbed7c1
/lib/modules/2.2.16-3.1smp/block/drbd.o: unresolved symbol
sock_recvmsg_R935ddbd6
/lib/modules/2.2.16-3.1smp/block/drbd.o: unresolved symbol
proc_register_R8b411fd1
/lib/modules/2.2.16-3.1smp/block/drbd.o: unresolved symbol
send_sig_info_Rf910c6d7
Thanks in Advance
Richard Mottershead
Senior Systems Engineer
McKessonHBOC - Nottingham
----------------------------------------------------------------------------
The information contained in this e-mail is confidential and is intended
only for the named recipient(s). If you are not the intended recipient you
must not copy, distribute, or take any action or reliance on it.
If you have received this e-mail in error, please notify the sender.
Any unauthorised disclosure of the information contained in this e-mail
is strictly prohibited.
----------------------------------------------------------------------------