quickie GFS with lock_nolock question

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster

[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux