On 04/05/12 15:53, Kaushal M wrote: > The clients should be enough. > But seeing as you mount didn't even happen, there might be some other > problem. > As Amar suggested, could you let us know what's in the client logs? They > should be in /var/log/glusterfs/<mnt-point>.log. Hi Kaushal, These are the logs from v 3.3 beta 3, and they'll be followed by the logs from v3.3 qa39. Note that in both cases I could successfully mount the volume using the same methods, if the primary vol server was up. So I don't think the messages about FUSE errors are relevant here. beta 3 (mount failed with backup vol server) [2012-05-04 11:43:06.722122] I [glusterfsd.c:1627:main] 0-/usr/sbin/glusterfs: S tarted running /usr/sbin/glusterfs version 3.3.0beta3 [2012-05-04 11:43:06.726136] E [socket.c:1724:socket_connect_finish] 0-glusterfs: connection to failed (Connection refused) [2012-05-04 11:43:06.726271] E [glusterfsd-mgmt.c:1689:mgmt_rpc_notify] 0-glusterfsd-mgmt: failed to connect with remote-host: Transport endpoint is not connected [2012-05-04 11:43:06.726291] I [glusterfsd-mgmt.c:1692:mgmt_rpc_notify] 0-glusterfsd-mgmt: -1 connect attempts left [2012-05-04 11:43:06.726443] W [glusterfsd.c:793:cleanup_and_exit] (-->/usr/lib/libgfrpc.so.0(rpc_transport_notify+0x27) [0x7fc2fb36b807] (-->/usr/lib/libgfrpc.so.0(rpc_clnt_notify+0x114) [0x7fc2fb36f7f4] (-->/usr/sbin/glusterfs() [0x40c146]))) 0-: received signum (1), shutting down [2012-05-04 11:43:06.726476] I [fuse-bridge.c:4556:fini] 0-fuse: Unmounting 'gluster'. [2012-05-04 11:43:06.726523] E [mount.c:397:fuse_mnt_umount] 0-glusterfs-fuse: fuse: failed to unmount gluster: No such file or directory [2012-05-04 11:43:06.731630] I [glusterfsd.c:1627:main] 0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version 3.3.0beta3 [2012-05-04 11:43:06.731843] E [fuse-bridge.c:4360:init] 0-fuse: Mountpoint gluster seems to have a stale mount, run 'umount gluster' and try again. [2012-05-04 11:43:06.731865] E [xlator.c:394:xlator_init] 0-fuse: Initialization of volume 'fuse' failed, review your volfile again Please note that despite the warning about stale mounts, I tried rebooting the machine even before trying again. Logs from qa39 (mount failed with backup vol server): [2012-05-04 17:21:34.837274] I [glusterfsd.c:1629:main] 0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version 3.3.0qa39 [2012-05-04 17:21:34.859494] E [mount.c:580:fuse_mount_sys] 0-glusterfs-fuse: calling mount [2012-05-04 17:21:34.859987] E [mount.c:583:fuse_mount_sys] 0-glusterfs-fuse: mount returned 0 [2012-05-04 17:21:34.860030] E [mount.c:625:fuse_mount_sys] 0-glusterfs-fuse: writing status [2012-05-04 17:21:34.860046] E [mount.c:637:fuse_mount_sys] 0-glusterfs-fuse: Mount child exiting [2012-05-04 17:21:37.858643] E [socket.c:1724:socket_connect_finish] 0-glusterfs: connection to failed (No route to host) [2012-05-04 17:21:37.858896] E [glusterfsd-mgmt.c:1741:mgmt_rpc_notify] 0-glusterfsd-mgmt: failed to connect with remote-host: Transport endpoint is not connected [2012-05-04 17:21:37.858921] I [glusterfsd-mgmt.c:1744:mgmt_rpc_notify] 0-glusterfsd-mgmt: -1 connect attempts left [2012-05-04 17:21:37.873617] W [glusterfsd.c:794:cleanup_and_exit] (-->/usr/lib/libgfrpc.so.0(rpc_transport_notify+0x27) [0x7fbd051cd897] (-->/usr/lib/libgfrpc.so.0(rpc_clnt_notify+0x114) [0x7fbd051d1874] (-->/usr/sbin/glusterfs() [0x40c816]))) 0-: received signum (1), shutting down [2012-05-04 17:21:37.873665] I [fuse-bridge.c:4649:fini] 0-fuse: Unmounting 'gluster'. [2012-05-04 17:21:37.873717] E [mount.c:397:fuse_mnt_umount] 0-glusterfs-fuse: fuse: failed to unmount gluster: No such file or directory [2012-05-04 17:21:47.918425] I [glusterfsd.c:1629:main] 0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version 3.3.0qa39 [2012-05-04 17:21:47.918568] E [fuse-bridge.c:4444:init] 0-fuse: Mountpoint gluster seems to have a stale mount, run 'umount gluster' and try again. [2012-05-04 17:21:47.918592] E [xlator.c:394:xlator_init] 0-fuse: Initialization of volume 'fuse' failed, review your volfile again
