On 09/06/2009 10:42 PM, Mark Mielke wrote:
This seems to happen about 50% of the time:
[root@wcarh035 ~]# ls /gluster/data
ls: cannot open directory /gluster/data: No such file or directory
[root@wcarh035 ~]# ls /gluster/data
00 06.fun 15 23.fun 32 40.fun 47 55.fun 64
00.fun 07 15.fun 24 32.fun 41 47.fun 56 64.fun
My current guess is that GlusterFS is saying the mount is complete to
AutoFS before the actual mount operation takes effect. 50% of the time
GlusterFS is able to complete the mount before AutoFS let's the user
continue, and all is well. The other 50% of the time, GlusterFS does
not quite finish the mount, and AutoFS gives the user a broken directory.
I might try and prove this by adding a sleep 5 to
/sbin/mount.glusterfs, although I do not consider this a valid
solution, as it just reduces the effect of the race - it does not
eliminate the race.
Uhh... Hmm... It already has a "sleep 3", and changing it to "sleep 5"
does not reduce the frequency of the problem. Changing it to "sleep 10"
also has no effect.
Why does it sometimes work and sometimes not?
Cheers,
mark
--
Mark Mielke<mark@xxxxxxxxx>
