<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/3.12.0"> </HEAD> <BODY> On Tue, 2008-01-08 at 22:39 -0500, Charlie Brady wrote: <BLOCKQUOTE TYPE=CITE> <PRE> On Tue, 8 Jan 2008, Gordan Bobic wrote: > Charlie Brady wrote: > > On Fri, 4 Jan 2008, Charlie Brady wrote: > > > >> I'm helping a colleague to collect information on an application lockup > >> problem on a two-node DLM/GFS cluster, with GFS on a shared SCSI array. > >> > >> I'd appreciate advice as to what information to collect next. > > > > Nobody have any advice? > > Shared SCSI as in iSCSI SAN or as in a shared SCSI bus with two machines > connected via a SCSI cable? The latter. I don't have the details immediately at hand, but it's all HP gear. A pair of DL380s with an external SCSI array (MSAxx), IIRC. </PRE> </BLOCKQUOTE> If it is a MSA20, MSA30 or MSA500 - they won't work with GFS. Shared SCSI bus isn't really shared, accesses lock the bus such that when one node accesses the storage the other node is locked out. GFS requires the ability to do shared concurrent access to the storage devices. This probably explains the hangs you were seeing. So, either get an iSCSI or fibre channel storage array, or go strictly with a failover storage architecture, such that only one node has the filesystem mounted at any one time. In that case, you don't need gfs anymore, just cluster suite to manage the failover. Kevin </BODY> </HTML>