<div dir="ltr">Hello Joe,<br>Your solution fixed the issue. However the .vol files were
not missing but instead have been regenerated (or modified) after
running the glusterd --xlator-option "*.upgrade=on" -N<br>Unfortunately,
I didn't do a backup of the vol files before running the command so I
can't see how those files actually changed, but I did a "ls" on the
/var/lib/glusterd/vols/dbs before and after the execution and can see
that the .vol files changed time stamp and size. I would of like to know
what exactly happened and if running this command is necessary after
an upgrade, probably it is a good idea to let know glusterfs guys to
included it in the "GlusterFS upgrade from 3.5.x to 3.6.X" documentation.<br><br>Thanks a lot!<br><br><br><br># ls -l /var/lib/glusterd/vols/dbs/ <br>total 44<br>drwxr-xr-x 2 root root 4096 Oct 27 15:10 bricks<br>-rw------- 1 root root 1796 Oct 27 15:10 dbs.10.0.1.103.data-exports-dbs_content.vol<br>-rw------- 1 root root 1796 Oct 27 15:10 dbs.10.0.1.104.data-exports-dbs_content.vol<br>-rw------- 1 root root 1298 Oct 27 15:10 dbs-fuse.vol<br>-rw------- 1 root root 16 Mar 27 14:25 cksum<br>-rw------- 1 root root 356 Oct 27 15:10 info<br>-rw------- 1 root root 84 Oct 27 15:10 <a href="http://node_state.info">node_state.info</a><br>-rw------- 1 root root 18 Mar 27 14:25 quota.cksum<br>-rw------- 1 root root 0 Mar 26 16:27 quota.conf<br>-rw------- 1 root root 12 Oct 27 15:10 rbstate<br>drwxr-xr-x 2 root root 4096 Mar 27 14:27 run<br>-rw------- 1 root root 1526 Oct 27 15:10 trusted-dbs-fuse.vol<br><br><br># glusterd --xlator-option "*.upgrade=on" -N<br>librdmacm: couldn't read ABI version.<br>librdmacm: assuming: 4<br>CMA: unable to get RDMA device list<br><br><br># ls -l /var/lib/glusterd/vols/dbs/<br>total 56<br>drwxr-xr-x 2 root root 4096 Oct 27 15:10 bricks<br>-rw------- 1 root root 1979 Mar 27 14:27 dbs.10.0.1.103.data-exports-dbs_content.vol<br>-rw------- 1 root root 1979 Mar 27 14:27 dbs.10.0.1.104.data-exports-dbs_content.vol<br>-rw------- 1 root root 1298 Oct 27 15:10 dbs-fuse.vol<br>-rw------- 1 root root 1352 Mar 27 14:27 dbs-rebalance.vol<br>-rw------- 1 root root 1352 Mar 27 14:27 dbs.tcp-fuse.vol<br>-rw------- 1 root root 16 Mar 27 14:27 cksum<br>-rw------- 1 root root 356 Oct 27 15:10 info<br>-rw------- 1 root root 84 Oct 27 15:10 <a href="http://node_state.info">node_state.info</a><br>-rw------- 1 root root 18 Mar 27 14:27 quota.cksum<br>-rw------- 1 root root 0 Mar 26 16:27 quota.conf<br>-rw------- 1 root root 12 Oct 27 15:10 rbstate<br>drwxr-xr-x 2 root root 4096 Mar 27 14:27 run<br>-rw------- 1 root root 1526 Oct 27 15:10 trusted-dbs-fuse.vol<br>-rw------- 1 root root 1580 Mar 27 14:27 trusted-dbs.tcp-fuse.vol<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 27, 2015 at 10:51 AM, Joe Julian <span dir="ltr"><<a href="mailto:joe@julianfamily.org" target="_blank">joe@julianfamily.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>We hit this in IRC recently. <br>
<br>
Somewhere during the upgrade process your .vol files were deleted (or renamed). Recreate them by stopping glusterd then running:<br>
<br>
glusterd --xlator-option "*.upgrade=on" -N<br>
<br><br><div class="gmail_quote"><div><div class="h5">On March 27, 2015 6:02:47 AM PDT, Kal Black <<a href="mailto:kaloblak@gmail.com" target="_blank">kaloblak@gmail.com</a>> wrote:</div></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div class="h5">
<div dir="ltr"><p dir="ltr">Hello,<br>
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?</p>
<p dir="ltr"># gluster volume info <br>
Volume Name: dbs<br>
Type: Replicate<br>
Volume ID: 84984920-2dde-4b40-8041-5d6d514adf37<br>
Status: Started<br>
Number of Bricks: 1 x 2 = 2<br>
Transport-type: tcp<br>
Bricks:<br>
Brick1: 10.0.1.103:/data/exports/dbs_content<br>
Brick2: 10.0.1.104:/data/exports/dbs_content</p>
<p dir="ltr">When I try to mount I got the following:</p>
<p dir="ltr"># mount -t glusterfs 10.0.1.103:/dbs /dbs_content<br>
WARNING: getfattr not found, certain checks will be skipped..<br>
Mount failed. Please check the log file for more details.<br></p>
<p dir="ltr">In the log I am getting:</p>
<p dir="ltr">[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)<br>
[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<br>
[2015-03-26 20:34:31.588053] E [glusterfsd-mgmt.c:1596:mgmt_getspec_cbk] 0-mgmt: failed to fetch volume file (key:/dbs)<br>
[2015-03-26 20:34:31.588330] W [glusterfsd.c:1194:cleanup_and_exit] (--> 0-: received signum (0), shutting down<br>
[2015-03-26 20:34:31.588373] I [fuse-bridge.c:5599:fini] 0-fuse: Unmounting '/dbs_content'.</p><p dir="ltr"><br></p><p>Best,</p></div>
<p style="margin-top:2.5em;margin-bottom:1em;border-bottom:1px solid #000"></p></div></div><pre><hr><br>Gluster-users mailing list<br><a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br><a href="http://www.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-users</a></pre></blockquote></div><span class="HOEnZb"><font color="#888888"><br>
-- <br>
Sent from my Android device with K-9 Mail. Please excuse my brevity.</font></span></div></blockquote></div><br></div>