I see below error in the log file. I think some how old mount is not
cleaned properly.
File: cli.log
[2014-12-30 11:23:19.553912] W
[cli-cmd-volume.c:886:gf_cli_create_auxiliary_mount] 0-cli: failed to
mount glusterfs client. Please check the log file
/var/log/glusterfs/quota-mount-patchy.log for more details
File: quota-mount-patchy.log
[2014-12-30 09:54:38.093890] I [MSGID: 100030] [glusterfsd.c:2027:main]
0-/build/install/sbin/glusterfs: Started running
/build/install/sbin/glusterfs version 3.7dev (args:
/build/install/sbin/glusterfs -s localhost --volfile-id patchy -l
/var/log/glusterfs/quota-mount-patchy.log -p /var/run/gluster/patchy.pid
--client-pid -5 /var/run/gluster/patchy/)
[2014-12-30 09:54:38.094546] E [fuse-bridge.c:5338:init] 0-fuse:
Mountpoint /var/run/gluster/patchy/ seems to have a stale mount, run
'umount /var/run/gluster/patchy/' and try again.
Can someone who have access to build machine, please clear the stale
mount on '/var/run/gluster/patchy/'?
Thanks,
Vijay
On Friday 02 January 2015 04:38 PM, Atin Mukherjee wrote:
Hi Vijai,
It seems like lots of regression test cases are failing due to auxiliary
mount failure in cli and thats because of left over auxiliary mount points.
[2014-12-30 10:21:15.875965] E [fuse-bridge.c:5338:init] 0-fuse:
Mountpoint /var/run/gluster/patchy/ seems to have a stale mount, run
'umount /var/run/gluster/patchy/' and try again.
Once such instance can be found at [1]
Can you please look into it?
~Atin
[1]
http://build.gluster.org/job/rackspace-regression-2GB-triggered/3406/consoleFull
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel
