[Bugs] [Bug 1157975] New: glusterd does not start if older volume exists

Tue Oct 28 07:08:37 UTC 2014

https://bugzilla.redhat.com/show_bug.cgi?id=1157975

            Bug ID: 1157975
           Summary: glusterd does not start if older volume exists
           Product: Red Hat Storage
           Version: 3.0
         Component: gluster-snapshot
          Severity: high
          Assignee: rjoseph at redhat.com
          Reporter: rabhat at redhat.com
        QA Contact: storage-qa-internal at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com,
                    nbalacha at redhat.com
        Depends On: 1119582

+++ This bug was initially created as a clone of Bug #1119582 +++

Description of problem:
Glusterd build using the latest master code base does not start if a volume
created when using the older gluster code is present on the node

Version-Release number of selected component (if applicable):

How reproducible:
Consistently

Steps to Reproduce:
1.Checkout code from git (I was using commit
d3f0de90d0c5166e63f5764d2f21703fd29ce976 ), build and install gluster. (make
install)
2.Create a volume and do some file operations.
3.Update to the latest glusterfs master code as on July 14 2014, build and
install gluster on the nodes.
4. Start glusterd 

Actual results:
Glusterd refuses to start

Expected results:
Glusterd should start

Additional info:

The following log messages are seen:
Jul 14 10:41:29 gluster-srv2 usr-local-etc-glusterfs-glusterd.vol[30355]:
[glusterd.c:1215:init] 0-management: Using /var/lib/glusterd as working
directory
Jul 14 10:41:29 gluster-srv2 usr-local-etc-glusterfs-glusterd.vol[30355]:
[rdma.c:4194:__gf_rdma_ctx_create] 0-rpc-transport/rdma: rdma_cm event channel
creation failed (No such device)
Jul 14 10:41:29 gluster-srv2 usr-local-etc-glusterfs-glusterd.vol[30355]:
[rdma.c:4482:init] 0-rdma.management: Failed to initialize IB Device
Jul 14 10:41:29 gluster-srv2 usr-local-etc-glusterfs-glusterd.vol[30355]:
[rpc-transport.c:333:rpc_transport_load] 0-rpc-transport: 'rdma' initialization
failed
Jul 14 10:41:29 gluster-srv2 usr-local-etc-glusterfs-glusterd.vol[30355]:
[rpcsvc.c:1524:rpcsvc_transport_create] 0-rpc-service: cannot create listener,
initing the transport failed
Jul 14 10:41:34 gluster-srv2 usr-local-etc-glusterfs-glusterd.vol[30355]:
[glusterd-store.c:2020:glusterd_restore_op_version] 0-glusterd: retrieved
op-version: 30600 
Jul 14 10:41:34 gluster-srv2 usr-local-etc-glusterfs-glusterd.vol[30355]:
[store.c:432:gf_store_handle_retrieve] 0-: Path corresponding to
/var/lib/glusterd/vols/holmes/snapd.info, returned error: (No such file or
directory)
Jul 14 10:41:34 gluster-srv2 usr-local-etc-glusterfs-glusterd.vol[30355]:
[glusterd-store.c:2124:glusterd_store_retrieve_snapd] 0-management: volinfo
handle is NULL
Jul 14 10:41:34 gluster-srv2 usr-local-etc-glusterfs-glusterd.vol[30355]:
[glusterd-store.c:3009:glusterd_store_retrieve_volumes] 0-: Unable to restore
volume: holmes
Jul 14 10:41:34 gluster-srv2 usr-local-etc-glusterfs-glusterd.vol[30355]:
[xlator.c:425lator_init] 0-management: Initialization of volume 'management'
failed, review your volfile again
Jul 14 10:41:34 gluster-srv2 usr-local-etc-glusterfs-glusterd.vol[30355]:
[graph.c:322:glusterfs_graph_init] 0-management: initializing translator failed 
Jul 14 10:41:34 gluster-srv2 usr-local-etc-glusterfs-glusterd.vol[30355]:
[graph.c:525:glusterfs_graph_activate] 0-graph: init failed

I reverted to the earlier gluster build, deleted the volume and then installed
the latest gluster code build. glusterd then started without issues.

--- Additional comment from Anand Avati on 2014-07-15 06:38:57 EDT ---

REVIEW: http://review.gluster.org/8310 (mgmt/glusterd: do not check for snapd
handle in restore if uss is disabled) posted (#1) for review on master by
Raghavendra Bhat (raghavendra at redhat.com)

--- Additional comment from Anand Avati on 2014-07-16 02:38:47 EDT ---

COMMIT: http://review.gluster.org/8310 committed in master by Kaushal M
(kaushal at redhat.com) 
------
commit dcc1696045f12127ff37e6312a04c0024c8a4e24
Author: Raghavendra Bhat <raghavendra at redhat.com>
Date:   Tue Jul 15 15:55:34 2014 +0530

    mgmt/glusterd: do not check for snapd handle in restore if uss is disabled

    Change-Id: I01afe64685a5794cce9265580c6c5de57a045201
    BUG: 1119582
    Signed-off-by: Raghavendra Bhat <raghavendra at redhat.com>
    Reviewed-on: http://review.gluster.org/8310
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Kaushal M <kaushal at redhat.com>

--- Additional comment from Niels de Vos on 2014-09-22 08:44:53 EDT ---

A beta release for GlusterFS 3.6.0 has been released. Please verify if the
release solves this bug report for you. In case the glusterfs-3.6.0beta1
release does not have a resolution for this issue, leave a comment in this bug
and move the status to ASSIGNED. If this release fixes the problem for you,
leave a note and change the status to VERIFIED.

Packages for several distributions should become available in the near future.
Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an
"updates-testing" repository) infrastructure for your distribution.

[1]
http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/

Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1119582
[Bug 1119582] glusterd does not start if older volume exists
-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=KC2lHv47aS&a=cc_unsubscribe