Bug 1220340 - Cannot start gluster volume
Summary: Cannot start gluster volume
Keywords:
Status: CLOSED DUPLICATE of bug 1220338
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: pre-release
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: qe_tracker_everglades
TreeView+ depends on / blocked
 
Reported: 2015-05-11 11:28 UTC by Stanislav Graf
Modified: 2015-05-11 11:35 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-05-11 11:35:57 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Stanislav Graf 2015-05-11 11:28:04 UTC
Description of problem:
=======================

# gluster volume info
 
Volume Name: DefaultVolume
Type: Distribute
Volume ID: 3822db8b-13b5-40ae-9001-18a08e6a38cb
Status: Created
Number of Bricks: 2
Transport-type: tcp
Bricks:
Brick1: hostname1:/rhs/brick1/b1
Brick2: hostname2:/rhs/brick1/b1
Options Reconfigured:
auth.allow: *
user.cifs: enable
nfs.disable: off
performance.readdir-ahead: on

# gluster volume start DefaultVolume
volume start: DefaultVolume: failed: Commit failed on localhost. Please check the log file for more details.
(exit code 1)

# tail /var/log/glusterfs/bricks/rhs-brick1-b1.log 
[2015-05-11 10:44:59.010107] E [graph.y:321:volume_end] 0-parser: "type" not specified for volume DefaultVolume-marker
[2015-05-11 10:44:59.010362] E [MSGID: 100026] [glusterfsd.c:2142:glusterfs_process_volfp] 0-: failed to construct the graph
[2015-05-11 10:44:59.010581] W [glusterfsd.c:1212:cleanup_and_exit] (--> 0-: received signum (0), shutting down
[2015-05-11 11:16:48.930810] I [MSGID: 100030] [glusterfsd.c:2288:main] 0-/usr/sbin/glusterfsd: Started running /usr/sbin/glusterfsd version 3.7.0beta1 (args: /usr/sbin/glusterfsd -s hostname2 --volfile-id DefaultVolume.hostname2.rhs-brick1-b1 -p /var/lib/glusterd/vols/DefaultVolume/run/hostname2-rhs-brick1-b1.pid -S /var/run/gluster/515899310f85ae7b9aabc7673a1fcdf6.socket --brick-name /rhs/brick1/b1 -l /var/log/glusterfs/bricks/rhs-brick1-b1.log --xlator-option *-posix.glusterd-uuid=e5e653b5-ce17-4ad0-8531-b12300212890 --brick-port 49157 --xlator-option DefaultVolume-server.listen-port=49157)
[2015-05-11 11:16:48.945579] I [event-epoll.c:629:event_dispatch_epoll_worker] 0-epoll: Started thread with index 1
[2015-05-11 11:16:48.953808] W [xlator.c:192:xlator_dynload] 0-xlator: /usr/lib64/glusterfs/3.7.0beta1/xlator/features/marker.so: cannot open shared object file: No such file or directory
[2015-05-11 11:16:48.953841] E [graph.y:212:volume_type] 0-parser: Volume 'DefaultVolume-marker', line 78: type 'features/marker' is not valid or not found on this machine
[2015-05-11 11:16:48.953866] E [graph.y:321:volume_end] 0-parser: "type" not specified for volume DefaultVolume-marker
[2015-05-11 11:16:48.954131] E [MSGID: 100026] [glusterfsd.c:2142:glusterfs_process_volfp] 0-: failed to construct the graph
[2015-05-11 11:16:48.954363] W [glusterfsd.c:1212:cleanup_and_exit] (--> 0-: received signum (0), shutting down


Version-Release number of selected component (if applicable):
=============================================================
glusterfs-3.7.0beta1-0.155.git72f80ae.el6.x86_64

How reproducible:
=================
100%

Steps to Reproduce:
===================
1. Create gluster volume
2. Try to start volume

Additional info:
================
I'll attach logs.

Comment 1 Stanislav Graf 2015-05-11 11:35:57 UTC

*** This bug has been marked as a duplicate of bug 1220338 ***


Note You need to log in before you can comment on or make changes to this bug.