Am Montag, 2. August 2010 13:40:30 schrieb Oliver Heinz: > I tried with a new 2.6.35 kernel, still won't work. > > No mandatory locking here: > > ls -al /srv/data/shared/locktest > -rw------- 1 root root 62 2. Aug 13:27 /srv/data/shared/locktest > > Any ideas? Should I try redhat-cluster 3.0.14? Just for the record: tried 3.0.14, same behaviour. Still "can't set lock : Function not implemented" Now I really run out of ideas, what to try next. Bye, Oliver > Am Donnerstag, 29. Juli 2010 19:07:12 schrieb rhurst@xxxxxxxxxxxxxxxxx: > > This may be a red herring, but can you check your permission bits on the > > file, /srv/data/shared/locktest > > > > If an 'ls -al locktest' shows it like 'rwxr-Sr-x' with the 'S' in the > > permissions for the group, that indicates mandatory locking -- I know GFS > > does/did not support that; I have not checked since my first encounter > > with that limitation from October 2006, so it may not be true today or > > with GFS2. Perhaps you can 'chmod g-s locktest' and try it again -- that > > had worked for me back then. > > > > > > -----Original Message----- > > From: linux-cluster-bounces@xxxxxxxxxx > > [mailto:linux-cluster-bounces@xxxxxxxxxx] On Behalf Of Oliver Heinz Sent: > > Thursday, July 29, 2010 8:56 AM > > To: linux-cluster@xxxxxxxxxx > > Subject: Re: GFS2 lockf(): Function not implemented > > > > > > Here's the 'strace -f' which might be more useful than the plain strace > > originally attached. > > > > > > Oliver > > > > Am Donnerstag, 29. Juli 2010 13:45:43 schrieb Oliver Heinz: > > > Am Donnerstag, 29. Juli 2010 13:27:09 schrieb Steven Whitehouse: > > > > Hi, > > > > > > > > On Thu, 2010-07-29 at 12:52 +0200, Oliver Heinz wrote: > > > > > Hi, > > > > > > > > > > I'm trying to get a pacemaker/gfs2 setup working. Everything works > > > > > good so far, but when applications try to do locks on the shared > > > > > gfs2 volumes I get "function not implemented". > > > > > > > > > > > > > > > For testing purposes I used the locktest script here: > > > > > http://nfsv4.bullopensource.org/tools/tests/locktest.php > > > > > > > > Was it trying to do mandatory locking? We don't support that. Can you > > > > strace the failing process and also show the exact error message that > > > > you are getting? > > > > > > That's what I get: > > > > > > root@server-c:~# ./locktests -n 2 -f /srv/data/shared/locktest > > > Init > > > process initalization > > > .... > > > -------------------------------------- > > > > > > TEST : TRY TO WRITE ON A READ LOCK:Master: can't set lock > > > > > > : Function not implemented > > > > > > Echec > > > > > > : Function not implemented > > > > > > strace output is attached. > > > > > > > > > The real world problem I'm facing is when I try to start vservers that > > > reside on the gfs2 Filesystem, strace output is also attached. > > > > > > root@server-c:~# vserver -v testshared start > > > secure-mount: lockf(): Function not implemented > > > Failed to update mtab-file > > > secure-mount: lockf(): Function not implemented > > > Failed to update mtab-file > > > secure-mount: lockf(): Function not implemented > > > Failed to update mtab-file > > > > > > > > > > > > > > > TIA, > > > Oliver > > > > -- > > Linux-cluster mailing list > > Linux-cluster@xxxxxxxxxx > > https://www.redhat.com/mailman/listinfo/linux-cluster > > -- > Linux-cluster mailing list > Linux-cluster@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/linux-cluster -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
