Bug 1119582
Summary: | glusterd does not start if older volume exists | |||
---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Nithya Balachandran <nbalacha> | |
Component: | core | Assignee: | Raghavendra Bhat <rabhat> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | mainline | CC: | bugs, gluster-bugs, hamiller | |
Target Milestone: | --- | |||
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.6.0beta1 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1157975 (view as bug list) | Environment: | ||
Last Closed: | 2014-11-11 08:37:05 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1157975 |
Description
Nithya Balachandran
2014-07-15 06:13:37 UTC
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) COMMIT: http://review.gluster.org/8310 committed in master by Kaushal M (kaushal) ------ commit dcc1696045f12127ff37e6312a04c0024c8a4e24 Author: Raghavendra Bhat <raghavendra> 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> Reviewed-on: http://review.gluster.org/8310 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Kaushal M <kaushal> 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/ This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.6.1, please reopen this bug report. glusterfs-3.6.1 has been announced [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html [2] http://supercolony.gluster.org/mailman/listinfo/gluster-users I see this BZ was closed, but I am seeing the following in a current customer case. All nodes upgraded from 3.0u1 to 3.0u3 are facing same symptoms. service glusterd start FAILS. Here is interesting part from debug mode: 2015-01-27 13:55:13.119036] D [store.c:608:gf_store_iter_get_next] 0-: Returning with 0 [2015-01-27 13:55:13.119043] D [store.c:608:gf_store_iter_get_next] 0-: Returning with 0 [2015-01-27 13:55:13.119051] D [store.c:608:gf_store_iter_get_next] 0-: Returning with -1 [2015-01-27 13:55:13.119066] D [glusterd-store.c:2414:glusterd_store_retrieve_bricks] 0-: Returning with 0 [2015-01-27 13:55:13.119086] E [store.c:432:gf_store_handle_retrieve] 0-: Path corresponding to /var/lib/glusterd/vols/user_home/snapd.info, returned error: (No such file or directory) [2015-01-27 13:55:13.119093] D [store.c:437:gf_store_handle_retrieve] 0-: Returning -1 [2015-01-27 13:55:13.119099] E [glusterd-store.c:2198:glusterd_store_retrieve_snapd] 0-management: volinfo handle is NULL [2015-01-27 13:55:13.119109] D [glusterd-utils.c:957:glusterd_volume_brickinfos_delete] 0-management: Returning 0 [2015-01-27 13:55:13.119117] D [store.c:458:gf_store_handle_destroy] 0-: Returning 0 [2015-01-27 13:55:13.119123] D [glusterd-utils.c:1001:glusterd_volinfo_delete] 0-management: Returning 0 [2015-01-27 13:55:13.119128] E [glusterd-store.c:3082:glusterd_store_retrieve_volumes] 0-: Unable to restore volume: user_home [2015-01-27 13:55:13.119136] D [glusterd-store.c:3114:glusterd_store_retrieve_volumes] 0-: Returning with -1 [2015-01-27 13:55:13.119142] D [glusterd-store.c:4308:glusterd_restore] 0-: Returning -1 [2015-01-27 13:55:13.119152] E [xlator.c:406:xlator_init] 0-management: Initialization of volume 'management' failed, review your volfile again [2015-01-27 13:55:13.119159] E [graph.c:322:glusterfs_graph_init] 0-management: initializing translator failed [2015-01-27 13:55:13.119165] E [graph.c:525:glusterfs_graph_activate] 0-graph: init failed [2015-01-27 13:55:13.119644] D [logging.c:1805:gf_log_flush_extra_msgs] 0-logging-infra: Log buffer size reduced. About to flush 3 extra log messages [2015-01-27 13:55:13.119662] D [logging.c:1808:gf_log_flush_extra_msgs] 0-logging-infra: Just flushed 3 extra log messages [2015-01-27 13:55:13.119809] W [glusterfsd.c:1182:cleanup_and_exit] (--> 0-: received signum (0), shutting down [2015-01-27 13:55:13.119827] D [glusterfsd-mgmt.c:2244:glusterfs_mgmt_pmap_signout] 0-fsd-mgmt: portmapper signout arguments not given File snapd.info is missing indeed. |