Following this thread a bit further I find that the jid is set to -1 because the +IBw-our+AF8-slot+IB0- value being passed to gdlm+AF8-recover+AF8-done is 0. dlm+AF8-recoverd is retrieving the clvmd lockspace and its ls+AF8-slot value is 0 (which is the source of our+AF8-slot): +AFs-73115.541794+AF0- name: clvmd +AFs-73115.541847+AF0- global+AF8-id: 4104eefa +AFs-73115.541893+AF0- node+AF8-count: 2 +AFs-73115.541937+AF0- low node: 1 +AFs-73115.541986+AF0- slot: 0 (00000000263d5268) +AFs-73115.542031+AF0- n'slots: 0 dlm+AF8-tool ls reports: dlm lockspaces name clvmd id 0x4104eefa flags 0x00000000 change member 2 joined 1 remove 0 failed 0 seq 1,1 members 1 2 Now to determine why ls+AF8-slot is 0. Neale On 10/13/14, 5:10 PM, +ACI-Neale Ferguson+ACI- +ADw-neale+AEA-sinenomine.net+AD4- wrote: +AD4-I put some debug code into the gfs2 module and I see it failing the mount +AD4-at this point: +AD4- +AD4-/+ACo- +AD4- +ACo- If user space has failed to join the cluster or some similar +AD4- +ACo- failure has occurred, then the journal id will contain a +AD4- +ACo- negative (error) number. This will then be returned to the +AD4- +ACo- caller (of the mount syscall). We do this even for spectator +AD4- +ACo- mounts (which just write a jid of 0 to indicate +ACI-ok+ACI- even +AD4-though +AD4- +ACo- the jid is unused in the spectator case) +AD4- +ACo-/ +AD4- if (sdp-+AD4-sd+AF8-lockstruct.ls+AF8-jid +ADw- 0) +AHs- +AD4- +AD4-Now to find out who+ALk-s stick -PERM into ls+AF8-jid. +AD4- +AD4-Neale +AD4- +AD4- +AD4--- +AD4-Linux-cluster mailing list +AD4-Linux-cluster+AEA-redhat.com +AD4-https://www.redhat.com/mailman/listinfo/linux-cluster
-- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
