Kal Black
2015-Mar-27 13:02 UTC
[Gluster-users] Can not mount volumes after upgrade to Gluster 3.6.6
Hello, After upgrading from Glusterfs 3.5 to Glusterfs 3.6.2, on Ubuntu 12.04, I am unable to mount gluster volumes any more. Found the same issue reported already and the answer suggested that a path to the volume is being used, during the mount attempt, instead of the volume name. This however seems not to be the case according to what I am seeing. Any ideas? # gluster volume info Volume Name: dbs Type: Replicate Volume ID: 84984920-2dde-4b40-8041-5d6d514adf37 Status: Started Number of Bricks: 1 x 2 = 2 Transport-type: tcp Bricks: Brick1: 10.0.1.103:/data/exports/dbs_content Brick2: 10.0.1.104:/data/exports/dbs_content When I try to mount I got the following: # mount -t glusterfs 10.0.1.103:/dbs /dbs_content WARNING: getfattr not found, certain checks will be skipped.. Mount failed. Please check the log file for more details. In the log I am getting: [2015-03-26 20:34:31.582757] I [MSGID: 100030] [glusterfsd.c:2018:main] 0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version 3.6.2 (args: /usr/sbin/glusterfs --volfile-server=10.0.1.103 --volfile-id=/dbs /dbs_content) [2015-03-26 20:34:31.587971] E [glusterfsd-mgmt.c:1494:mgmt_getspec_cbk] 0-glusterfs: failed to get the 'volume file' from server [2015-03-26 20:34:31.588053] E [glusterfsd-mgmt.c:1596:mgmt_getspec_cbk] 0-mgmt: failed to fetch volume file (key:/dbs) [2015-03-26 20:34:31.588330] W [glusterfsd.c:1194:cleanup_and_exit] (--> 0-: received signum (0), shutting down [2015-03-26 20:34:31.588373] I [fuse-bridge.c:5599:fini] 0-fuse: Unmounting '/dbs_content'. Best, -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20150327/0cb8b1bb/attachment.html>
Kal Black
2015-Mar-27 13:38 UTC
[Gluster-users] Can not mount volumes after upgrade to Gluster 3.6.6
In case this would help, I am posting my glustershd.log. There are references to "Using Program GlusterFS 3.3, Num (1298437), Version (330)" which looks weird to me. The Glusterfs packages I have currenlty installed on my servers are: # dpkg -l | grep gluster ii glusterfs-client 3.6.2-ubuntu1~trusty3 amd64 clustered file-system (client package) ii glusterfs-common 3.6.2-ubuntu1~trusty3 amd64 GlusterFS common libraries and translator modules ii glusterfs-server 3.6.2-ubuntu1~trusty3 amd64 clustered file-system (server package # cat glustershd.log [2015-03-27 13:17:02.592377] W [socket.c:611:__socket_rwv] 0-glusterfs: readv on 127.0.0.1:24007 failed (No data available) [2015-03-27 13:17:04.290821] W [glusterfsd.c:1194:cleanup_and_exit] (--> 0-: received signum (15), shutting down [2015-03-27 13:19:20.296302] I [MSGID: 100030] [glusterfsd.c:2018:main] 0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version 3.6.2 (args: /usr/sbin/glusterfs -s localhost --volfile-id gluster/glustershd -p /var/lib/glusterd/glustershd/run/glustershd.pid -l /var/log/glusterfs/glustershd.log -S /var/run/1b1a5942b3345e36119e9eb4986a6137.socket --xlator-option *replicate*.node-uuid=10d77d7b-e893-4be0-b09c-2cb0f0a46270) [2015-03-27 13:19:20.386644] I [graph.c:269:gf_add_cmdline_options] 0-dbs-replicate-0: adding option 'node-uuid' for volume 'dbs-replicate-0' with value '10d77d7b-e893-4be0-b09c-2cb0f0a46270' [2015-03-27 13:19:20.397051] I [client.c:2280:notify] 0-dbs-client-0: parent translators are ready, attempting connect on transport [2015-03-27 13:19:20.397336] I [client.c:2280:notify] 0-dbs-client-1: parent translators are ready, attempting connect on transport Final graph: +------------------------------------------------------------------------------+ 1: volume dbs-client-0 2: type protocol/client 3: option ping-timeout 42 4: option remote-host 10.0.1.103 5: option remote-subvolume /data/exports/dbs_content 6: option transport-type socket 7: option username 108ea0a8-5c0a-44cd-8f4a-75dbecb186cd 8: option password 333c6934-4179-43f5-bcd8-80cdf478e5aa 9: end-volume 10: 11: volume dbs-client-1 12: type protocol/client 13: option ping-timeout 42 14: option remote-host 10.0.1.104 15: option remote-subvolume /data/exports/dbs_content 16: option transport-type socket 17: option username 108ea0a8-5c0a-44cd-8f4a-75dbecb186cd 18: option password 333c6934-4179-43f5-bcd8-80cdf478e5aa 19: end-volume 20: 21: volume dbs-replicate-0 22: type cluster/replicate 23: option node-uuid 10d77d7b-e893-4be0-b09c-2cb0f0a46270 24: option background-self-heal-count 0 25: option metadata-self-heal on 26: option data-self-heal on 27: option entry-self-heal on 28: option self-heal-daemon on 29: option iam-self-heal-daemon yes 30: subvolumes dbs-client-0 dbs-client-1 31: end-volume 32: 33: volume glustershd 34: type debug/io-stats 35: subvolumes dbs-replicate-0 36: end-volume 37: +------------------------------------------------------------------------------+ [2015-03-27 13:19:20.398040] E [client-handshake.c:1496:client_query_portmap_cbk] 0-dbs-client-0: failed to get the port number for remote subvolume. Please run 'gluster volume status' on server to see if brick process is running. [2015-03-27 13:19:20.398134] I [client.c:2215:client_rpc_notify] 0-dbs-client-0: disconnected from dbs-client-0. Client process will keep trying to connect to glusterd until brick's port is available [2015-03-27 13:19:20.398306] I [rpc-clnt.c:1761:rpc_clnt_reconfig] 0-dbs-client-1: changing port to 49152 (from 0) [2015-03-27 13:19:20.398958] I [client-handshake.c:1413:select_server_supported_programs] 0-dbs-client-1: Using Program GlusterFS 3.3, Num (1298437), Version (330) [2015-03-27 13:19:20.399288] I [client-handshake.c:1200:client_setvolume_cbk] 0-dbs-client-1: Connected to dbs-client-1, attached to remote volume '/data/exports/dbs_content'. [2015-03-27 13:19:20.399301] I [client-handshake.c:1210:client_setvolume_cbk] 0-dbs-client-1: Server and Client lk-version numbers are not same, reopening the fds [2015-03-27 13:19:20.399334] I [MSGID: 108005] [afr-common.c:3552:afr_notify] 0-dbs-replicate-0: Subvolume 'dbs-client-1' came back up; going online. [2015-03-27 13:19:20.399456] I [client-handshake.c:188:client_set_lk_version_cbk] 0-dbs-client-1: Server lk version = 1 [2015-03-27 13:19:24.301326] I [rpc-clnt.c:1761:rpc_clnt_reconfig] 0-dbs-client-0: changing port to 49152 (from 0) [2015-03-27 13:19:24.301739] I [client-handshake.c:1413:select_server_supported_programs] 0-dbs-client-0: Using Program GlusterFS 3.3, Num (1298437), Version (330) [2015-03-27 13:19:24.301893] I [client-handshake.c:1200:client_setvolume_cbk] 0-dbs-client-0: Connected to dbs-client-0, attached to remote volume '/data/exports/dbs_content'. [2015-03-27 13:19:24.301906] I [client-handshake.c:1210:client_setvolume_cbk] 0-dbs-client-0: Server and Client lk-version numbers are not same, reopening the fds [2015-03-27 13:19:24.302012] I [client-handshake.c:188:client_set_lk_version_cbk] 0-dbs-client-0: Server lk version = 1 Best, On Fri, Mar 27, 2015 at 9:02 AM, Kal Black <kaloblak at gmail.com> wrote:> Hello, > After upgrading from Glusterfs 3.5 to Glusterfs 3.6.2, on Ubuntu 12.04, I > am unable to mount gluster volumes any more. Found the same issue reported > already and the answer suggested that a path to the volume is being used, > during the mount attempt, instead of the volume name. This however seems > not to be the case according to what I am seeing. Any ideas? > > # gluster volume info > Volume Name: dbs > Type: Replicate > Volume ID: 84984920-2dde-4b40-8041-5d6d514adf37 > Status: Started > Number of Bricks: 1 x 2 = 2 > Transport-type: tcp > Bricks: > Brick1: 10.0.1.103:/data/exports/dbs_content > Brick2: 10.0.1.104:/data/exports/dbs_content > > When I try to mount I got the following: > > # mount -t glusterfs 10.0.1.103:/dbs /dbs_content > WARNING: getfattr not found, certain checks will be skipped.. > Mount failed. Please check the log file for more details. > > In the log I am getting: > > [2015-03-26 20:34:31.582757] I [MSGID: 100030] [glusterfsd.c:2018:main] > 0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version 3.6.2 > (args: /usr/sbin/glusterfs --volfile-server=10.0.1.103 --volfile-id=/dbs > /dbs_content) > [2015-03-26 20:34:31.587971] E [glusterfsd-mgmt.c:1494:mgmt_getspec_cbk] > 0-glusterfs: failed to get the 'volume file' from server > [2015-03-26 20:34:31.588053] E [glusterfsd-mgmt.c:1596:mgmt_getspec_cbk] > 0-mgmt: failed to fetch volume file (key:/dbs) > [2015-03-26 20:34:31.588330] W [glusterfsd.c:1194:cleanup_and_exit] (--> > 0-: received signum (0), shutting down > [2015-03-26 20:34:31.588373] I [fuse-bridge.c:5599:fini] 0-fuse: > Unmounting '/dbs_content'. > > > Best, >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20150327/a2e7822d/attachment.html>
Joe Julian
2015-Mar-27 14:51 UTC
[Gluster-users] Can not mount volumes after upgrade to Gluster 3.6.6
We hit this in IRC recently. Somewhere during the upgrade process your .vol files were deleted (or renamed). Recreate them by stopping glusterd then running: glusterd --xlator-option "*.upgrade=on" -N On March 27, 2015 6:02:47 AM PDT, Kal Black <kaloblak at gmail.com> wrote:>Hello, >After upgrading from Glusterfs 3.5 to Glusterfs 3.6.2, on Ubuntu 12.04, >I >am unable to mount gluster volumes any more. Found the same issue >reported >already and the answer suggested that a path to the volume is being >used, >during the mount attempt, instead of the volume name. This however >seems >not to be the case according to what I am seeing. Any ideas? > ># gluster volume info >Volume Name: dbs >Type: Replicate >Volume ID: 84984920-2dde-4b40-8041-5d6d514adf37 >Status: Started >Number of Bricks: 1 x 2 = 2 >Transport-type: tcp >Bricks: >Brick1: 10.0.1.103:/data/exports/dbs_content >Brick2: 10.0.1.104:/data/exports/dbs_content > >When I try to mount I got the following: > ># mount -t glusterfs 10.0.1.103:/dbs /dbs_content >WARNING: getfattr not found, certain checks will be skipped.. >Mount failed. Please check the log file for more details. > >In the log I am getting: > >[2015-03-26 20:34:31.582757] I [MSGID: 100030] [glusterfsd.c:2018:main] >0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version >3.6.2 >(args: /usr/sbin/glusterfs --volfile-server=10.0.1.103 >--volfile-id=/dbs >/dbs_content) >[2015-03-26 20:34:31.587971] E >[glusterfsd-mgmt.c:1494:mgmt_getspec_cbk] >0-glusterfs: failed to get the 'volume file' from server >[2015-03-26 20:34:31.588053] E >[glusterfsd-mgmt.c:1596:mgmt_getspec_cbk] >0-mgmt: failed to fetch volume file (key:/dbs) >[2015-03-26 20:34:31.588330] W [glusterfsd.c:1194:cleanup_and_exit] >(--> >0-: received signum (0), shutting down >[2015-03-26 20:34:31.588373] I [fuse-bridge.c:5599:fini] 0-fuse: >Unmounting >'/dbs_content'. > > >Best, > > >------------------------------------------------------------------------ > >_______________________________________________ >Gluster-users mailing list >Gluster-users at gluster.org >http://www.gluster.org/mailman/listinfo/gluster-users-- Sent from my Android device with K-9 Mail. Please excuse my brevity. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20150327/ae60c707/attachment.html>