On Wed, 9 Mar 2005, Peter T. Breuer wrote:
> Well, bear in mind that changes made to the export on server A
> without initiating them from the client on server B will not be seen by
> the kernel on server B unless that kernel does absolutely NO caching!
> I.e. it reads data anew without cconsulting its own buffers every time
> it neeeds to know something.
>
> Can you guarantee that? It sounds like you can, since you are using
> serial access.
Well, I don't know, really.
Usually one would use an external SCSI RAID storage, that can be connected
to two servers. The Cluster manager on both servers would be configured to
use the same device on that storage.
My guess is that same 'rules' regarding kernel and caching apply in that
case too, right? So if the Cluster manager is designed to deal with that
in this case, it should do the same with ENBD...
> There is still a danger of races between two kernels to write the same
> stuff, but maybe your softare can hande that. It would only require a
> single common lock.
I hope that the Cluster manager software is designed to deal with that.
D:
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.