tensai at zmonkey.org
Thu Jan 5 17:46:16 CET 2006
On Thu, 2006-01-05 at 09:45 -0500, Chip Burke wrote:
> Exactly. I was trying to replicate /boot with 'meta-data internal' which
> would cause it to die being that the space wasn't available. I am slowly
> getting my head around the whole process.
> However, I can't seem to mount the drbd device. I edited my fstab from
> /dev/hda2 / ext3 defaults 1 1
> /dev/drbd0 / ext3 defaults 1 1
> and it does not like it. When I try to start drbd manually using 'service
> brbd start' or 'drbdadm up all', I get an error that /dev/hda2 is already
> mounted. So I am a bit confused as to how to actually mount the /dev/drbdx
The error means exactly what it says. /dev/hda2 is already mounted and
DRBD will refuse to start in that situation. DRBD must ensure that it
alone can write to the underlying block device, otherwise you *will* get
data corruption. That's a Bad Thing(tm).
> Essentially I want the root file system to be identical between two
> boxes for a failover situation. Am I headed in the right direction?
I recommend you reconsider your goals. Do you really need the entire
system replicated? Doing so gets complicated quickly because to
mount /dev/drbd0 you have to umount /dev/hda2. Well, where is /etc? It's
on /dev/hda2. How can DRBD read /etc/drbd.conf if the disk isn't
mounted? That doesn't even get into problems of IP address
I have heard rumors of it being possible. I believe Linbit offers a
premium service to that effect. If that's really what you want, I
recommend shelling out the cash because otherwise you're going to end up
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.linbit.com/pipermail/drbd-user/attachments/20060105/ac9cd425/attachment.pgp
More information about the drbd-user