[Linux-cluster] quickie GFS with lock_nolock question

[rhurst at bidmc.harvard.edu]

For example, in /etc/fstab an entry could look like:
 
/dev/VGCCC/lvolshare    /cluster/share          gfs     lockproto=lock_nolock  0 0
An ad-hoc mount could look like:
 
mount -t gfs -o lockproto=lock_nolock /dev/VGCCC/lvolshare /cluster/share
Make certain that this filesystem is not mounted anywhere else before overriding, because it will corrupt.
 
 
Robert Hurst, Sr. Caché Administrator
Beth Israel Deaconess Medical Center
1135 Tremont Street, REN-7
Boston, Massachusetts   02120-2140
617-754-8754 · Fax: 617-754-8730 · Cell: 401-787-3154
Any technology distinguishable from magic is insufficiently advanced.

________________________________

From: linux-cluster-bounces at redhat.com on behalf of Jason Welsh
Sent: Wed 7/22/2009 7:15 PM
To: linux clustering
Subject: [Linux-cluster] quickie GFS with lock_nolock question



we have a funky custom application that doesnt seem to like
reading/writing to the shared GFS filesystem we have on our 2node
cluster. someone at the vendor suggested just having the main node mount
the GFS filesystem with "lock_nolock" to see if that would fix the problem.
What is the correct way to go through the motions to do this? because
currently they both mount up the gfs partition and I believe its a
dependency for the other services. feel free to direct me to the right
FM to RTFM.

Jason


--
Linux-cluster mailing list
Linux-cluster at redhat.com
https://www.redhat.com/mailman/listinfo/linux-cluster



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20090722/b4929c72/attachment.htm>