Summary: Re: [ILUG] NBD's, lihux-HA, GFS/GNBD vs. DRBD/heartbeat

[John Moylan]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Just forwarding this to the list for completeness, as I seem to only
have sent it to Paul yesterday.

...

Thanks for all of the feedback. A summary of which follows.

*Keep things simple by using user space code where appropriate. Don't
use ethernet bonding.

*Don't use SMP for IO bound tasks (although in this case I think I will,
(for rsync, NFS,SMB overhead. I will be using an enterprise distro
CENTOS 4, so I'm not too worried about SMP stability.)

*DRBD, GFS/GNBD and EVMS could all candidates for network block devices,
(they have not been knocked that is;), I am leaning towards a QA'd for
RHAS4 GFS - when it arrives, and I'll be testing DRBD in the meantime)
NBD is probably a no-no, and I think ENBD is not really suitable either.
(http://lists.linux-ha.org/pipermail/linux-ha/2001-June/003072.html)

J


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFCJDm7HgDLUzVQ7OARAlPPAKDbS5HY5KIOuhhzm7OmQQtfFnV66wCbBbrB
RXMzS3GQ8v20qJ1XAzVy6Dg=3D
=3D/2eQ
-----END PGP SIGNATURE-----

***************************************************************************=
***
The information in this e-mail is confidential and may be legally privilege=
d.
It is intended solely for the addressee. Access to this e-mail by anyone el=
se
is unauthorised. If you are not the intended recipient, any disclosure,
copying, distribution, or any action taken or omitted to be taken in relian=
ce
on it, is prohibited and may be unlawful.
Please note that emails to, from and within RTE may be subject to the Freed=
om
of Information Act 1997 and may be liable to disclosure.
***************************************************************************=
***