I think the problem is actually a FC-SAN problem, but I just wanted to
follow up on this particular message.
GFS panics when Linux loses the SCSI device. The SCSI device disapepars
because of a SAN communications failure. I don't think it is a GFS
problem. Thanks for the info on that message.
tc
Adam Manthei
<amanthei@xxxxxxxxxx> To: Discussion of clustering software components including GFS
Sent by: <linux-cluster@xxxxxxxxxx>
linux-cluster-bounces cc: (bcc: Tom Currie/teamics)
@redhat.com Subject: Re: [Linux-cluster] unusual GFS problem
08/24/04 10:36 AM
Please respond to
Discussion of
clustering software
components including
GFS
On Tue, Aug 24, 2004 at 09:51:58AM -0500, tomc@xxxxxxxxxxx wrote:
> Looking for some direction on this, please. What is this message
telling
> me? This node was the master in a three node setup:
The message is telling you that you turned on the "Locking" gulm verbosity
flag :) The short answer is that it's just letting you know you have lock
contention. These messages are rather common and can be ignored
(especially
if your applications are modifying common files or directories from more
than one node).
>
>
> Aug 24 03:11:21 lvs2 lock_gulmd_LT000[1332]: Asking for exl, where I hold
> the lock Shr, and someone else is
> queued before me.
> Aug 24 03:11:21 lvs2 lock_gulmd_LT000[1332]: Asking for exl, where I hold
> the lock Shr, and someone else is
> queued before me.
>
> This repeated for about 3 hours, then one of the other nodes had a GFS
> panic and had to be rebooted. Any suggestions would be appreciated.
Without the panic message and relevant syslog messages, we can't really
help
you.
--
Adam Manthei <amanthei@xxxxxxxxxx>
--
Linux-cluster@xxxxxxxxxx
http://www.redhat.com/mailman/listinfo/linux-cluster
