[Bugs] [Bug 1320110] New: when multiple peers and a running volume, glusterd restart failed.

bugzilla at redhat.com bugzilla at redhat.com
Tue Mar 22 10:31:52 UTC 2016


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

            Bug ID: 1320110
           Summary: when multiple peers and a running volume, glusterd
                    restart failed.
           Product: GlusterFS
           Version: mainline
         Component: glusterd
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: iesool at 126.com
                CC: bugs at gluster.org



​I got a problem, steps as follows:
    ​1)gluster peer probe node-2,   gluster peer probe node-3;
    ​2)gluster vol create test node-{1,2,3}:/disk1 force;
    ​3)gluster vol start test;
    ​4)mount.glusterfs 127.0.0.1:/test /test/;
    ​
  then  I try to /etc/init.d/glusterd restart, but glusterd restart failed.
  this is log:
[2016-03-22 18:35:56.301154] I [MSGID: 106513]
[glusterd-store.c:2058:glusterd_restore_op_version] 0-glusterd: retrieved
op-version: 40000
[2016-03-22 18:35:57.084676] I [MSGID: 106544]
[glusterd.c:155:glusterd_uuid_init] 0-management: retrieved UUID:
136c8841-c5fe-41de-a5ad-c8939016ea2d
[2016-03-22 18:35:57.092168] E [MSGID: 106201]
[glusterd-store.c:3071:glusterd_store_retrieve_volumes] 0-management: Unable to
restore volume: test
[2016-03-22 18:35:57.092459] E [MSGID: 101019] [xlator.c:430:xlator_init]
0-management: Initialization of volume 'management' failed, review your volfile
again
[2016-03-22 18:35:57.092499] E [MSGID: 101066]
[graph.c:324:glusterfs_graph_init] 0-management: initializing translator failed
[2016-03-22 18:35:57.092523] E [MSGID: 101176]
[graph.c:670:glusterfs_graph_activate] 0-graph: init failed
[2016-03-22 18:35:57.093132] W [glusterfsd.c:1251:cleanup_and_exit]
(-->/usr/sbin/glusterd(glusterfs_volumes_init+0xee) [0x40a470]
-->/usr/sbin/glusterd(glusterfs_process_volfp+0x19d) [0x40a37d]
-->/usr/sbin/glusterd(cleanup_and_exit+0x88) [0x408137] ) 0-: received signum
(0), shutting down

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list