From owner-freebsd-cluster Mon Aug 21 3:55: 3 2000 Delivered-To: freebsd-cluster@freebsd.org Received: from sanson.reyes.somos.net (freyes.static.inch.com [216.223.199.224]) by hub.freebsd.org (Postfix) with ESMTP id 9D9E037B42C for ; Mon, 21 Aug 2000 03:54:58 -0700 (PDT) Received: from tomasa (tomasa.reyes.somos.net [10.0.0.11]) by sanson.reyes.somos.net (8.9.3/8.9.3) with SMTP id GAA21318; Mon, 21 Aug 2000 06:46:17 -0400 (EDT) (envelope-from fran@reyes.somos.net) Message-Id: <200008211046.GAA21318@sanson.reyes.somos.net> From: "Francisco Reyes" To: "Andrzej Bialecki" Cc: "cluster@freebsd.org" Date: Mon, 21 Aug 2000 06:55:56 -0400 Reply-To: "Francisco Reyes" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 98 (4.10.2222) In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: Sharing disks for failover clustering Sender: owner-freebsd-cluster@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 21 Aug 2000 10:00:08 +0200 (CEST), Andrzej Bialecki wrote: >Why, if I may ask? If you really want this, you quickly run into all sorts >of nasty locking problems - with NFS as well (most implementations of >lockd do quite poor job). Unless you want to build SSI (single system >image) cluster, you usually want 1 (one) instance of the application >running, and another on the second machine in a standby state (i.e. NOT >accessing the same data). Then, during failover, the first machine >unmounts the shared disk, and the second mounts it, and everybody is happy >Am I missing something? Crashes usually happen when nobody is around to do the necessary work to change the machines (i.e. vacation, weekend...). It is just the nature of the beast. As a far second best is to try to document things so "anyone" in the IT department can do the changes/reboot. francisco Moderator of the Corporate BSD list http://www.egroups.com/group/BSD_Corporate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-cluster" in the body of the message