Christos Triantafillou wrote: >> You mean that the users are using the default lockspace even >> though the lockspace that was created by root was a different one? >> Strange. > > yes, that is what is happenning: > I have got these devices: > crwxrwxrwx 1 root root 10, 62 May 30 21:32 dlm-control > crwxrwxrwx 1 root root 10, 61 May 30 21:32 dlm_default > crwxrwxrwx 1 root root 10, 61 May 31 17:03 dlm_kobe > > and I can now run all the user tests as a non-root user: > # lstest -o -r -l default > Opening lockspace default > locking LOCK-NAME EX ...ast called, status = 0, lkid=103a8 > unlocking LOCK-NAME...ast called, status = 65538, lkid=103a8 > > but > # lstest -o -l default > Opening lockspace default > locking LOCK-NAME EX ...ast called, status = 0, lkid=100cf > unlocking LOCK-NAME...ast called, status = 65538, lkid=100cf > Releasing ls default > release ls: Operation not permitted > It looks like the default lockspace didn't get released when the all references to it disappeared (unless you have something holding it open!). I'm not sure how that might happen -- patrick -- Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
