Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
I am using drbd-0.7.0-59.22 (the default) with SLES 9. The linux kernel
version is 2.6.5-7.97 which is the default kernel bundled with this
distro.
I am using a 2-node cluster, /dev/sdb1 is the partition on both nodes, the
partition is kept to the same size on both nodes (verified using parted)
and ext3 is the fs-type I created on both nodes.
I could - using "drbdadm -- --do-what-I-say primary all" make one of the
nodes primary, the other automatically syncs up as a secondary and the
syncing goes on fine with pleasing messages in /proc/drbd and
/var/log/messages.
Since this is an older drbd version , it still borrows the /dev/nbd0 major
device no. I tried to search all available documentation but this is still
unclear to me :
1. After "insmod drbd.ko" and "drbdadm up all" (which I do instead of
/etc/init.d/drbd start) - shouldn't I be able to see the lower device
mounted?
The drbd.conf details for the nodes are :
resource drbd0 {
protocol C;
on node1 {
device /dev/nb0;
disk /dev/sdb1;
address 192.168.1.1:7788;
meta-disk internal;
}
//similar for node2
My problem is that I am not able to see /dev/nb0 mounted in /proc/mounts
or via the mount command. If I try to mount it via : "mount /dev/nb0
/mnt1" or something like that, it obvoiously cribs that the device is
already in use. Since I already started drbd.
I initially had a line in /etc/fstab which specified /dev/nb0 to be
mounted on /mnt1 with the "noauto" option, but later removed it, since I
want to try out drbd first without heartbeat or anything else. Both cases
produced the same problem.
Can anyone clarify this?
Thanks,
Anand
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20041004/910ed507/attachment.htm>