[Linux-cluster] quickie GFS with lock_nolock question

[Jason Welsh]

Charlie Brady wrote:
>
> On Wed, 22 Jul 2009, Jason Welsh wrote:
>
>> we have a funky custom application that doesnt seem to like
>> reading/writing to the shared GFS filesystem ...
>
> What is your definition of "doesn't seem to like reading/writing"?
>
>> 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.
>
> "fix" the problem? Or just hide it?

well, we are trying to test to see if thats the real problem or not.. It
might not be.
to make it simple, I just added that argument in the fstab on the first
server and shutdown the second server.
the question  I was trying to ask was without shutting down and
rebooting the servers, whats the right way to back both servers out of
the clustered service and manually mount up the GFS partition on the
first node.. I tried doing the "cman_tool leave remove"
but I got the error that there were still services running, I tried
shutting down everything, but still had like 3 lingering..
at this point, I just shut one down and rebooted the other with the
correct mount options and everything is fine now for our testing..
I will hopefully know later today if the application will behave with
its data on GFS volume mounted by the single node.

thanks/regards,
Jason