>Use fence_manual ... but it is not supported officially by TUV in >production environments ... Do not use that... How does that actually fence the offending node when it needs to? The concept of fencing is for the preservation of data integrity, circumventing it with a manual fence is useful only for testing, if you need to fence an errant node in production and don't, it might just corrupt your shared storage. Sigh... Make a firewall provision, it's imperative you get fencing right. _______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
Re: ESXi 4.1 and Cluster Fencing
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: "centos@xxxxxxxxxx" <centos@xxxxxxxxxx>
- Subject: Re: ESXi 4.1 and Cluster Fencing
- From: "Joseph L. Casale" <jcasale@xxxxxxxxxxxxxxxxx>
- Date: Wed, 23 Mar 2011 22:50:27 +0000
- Accept-language: en-US
- Delivered-to: centos@xxxxxxxxxx
- In-reply-to: <4D8A74D4.7030707@xxxxxxxxx>
- Thread-index: AcvpqGgrure0QpRBSW6IROiq9m92PQAM/s8AAAwRHPA=
- Thread-topic: ESXi 4.1 and Cluster Fencing
- References:
- ESXi 4.1 and Cluster Fencing
- From: Machin, Greg
- Re: ESXi 4.1 and Cluster Fencing
- From: carlopmart
- ESXi 4.1 and Cluster Fencing
- Prev by Date: How does Linux Repair actually work
- Next by Date: Re: How does Linux Repair actually work
- Previous by thread: Re: ESXi 4.1 and Cluster Fencing
- Next by thread: How does Linux Repair actually work
- Index(es):
 |