[DRBD-user] Disk Corruption = DRBD Failure?

[Charles Kozler]

Haven't read it yet though I will later today.

Having not ready any of the documentation of the underlying processes/workings, all of my understandings were purely based on assumptions from my basic use with DRBD- that said, thank you for all your insight and I will let you know later my understandings :)


Sent from my Verizon Wireless BlackBerry

-----Original Message-----
From: Florian Haas <florian at hastexo.com>
Sender: drbd-user-bounces at lists.linbit.com
Date: Fri, 14 Oct 2011 09:08:17 
To: <drbd-user at lists.linbit.com>
Subject: Re: [DRBD-user] Disk Corruption = DRBD Failure?

On 2011-10-12 20:30, Charles Kozler wrote:
> I will re-read the DRBD Funadmentals- the way I understood it was
> basically if you were writing to node1 it wouldn't put the data through
> a TCP socket and would actually just write directly to the block device
> and that TCP was usually only used for the actual replicating and data
> integrity conversation between the hosts.  My understanding now is that
> for all hosts included in the resource definition it will put the data
> into that socket - including the host you're writing from (eg: if I
> wrote to /dev/drbd0 on host1 it will go through the socket to write the
> data still to write it to the underlying block device-

Er, no. It won't.

> I had originally
> thought it would skip the TCP socket write and write directly to the
> block device).

For the _local_ write, of course it doesn't go through the TCP socket.
Why should it? That would be braindead. Also, given the documentation,
what makes you think so? I ask because I wrote it, and if there's
anything horribly unclear in there I'd be happy to fix it.

Did you look at the illustration in the Fundamentals chapter?

Florian

-- 
Need help with High Availability?
http://www.hastexo.com/now
_______________________________________________
drbd-user mailing list
drbd-user at lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-user