On Thu, Jul 6, 2017 at 2:16 PM, Atin Mukherjee <amukherj@xxxxxxxxxx> wrote:
On Thu, Jul 6, 2017 at 5:26 PM, Gianluca Cecchi <gianluca.cecchi@xxxxxxxxx> wrote:On Thu, Jul 6, 2017 at 8:38 AM, Gianluca Cecchi <gianluca.cecchi@xxxxxxxxx> wrote:Eventually I can destroy and recreate this "export" volume again with the old names (ovirt0N.localdomain.local) if you give me the sequence of commands, then enable debug and retry the reset-brick commandGianlucaSo it seems I was able to destroy and re-create.Now I see that the volume creation uses by default the new ip, so I reverted the hostnames roles in the commands after putting glusterd in debug mode on the host where I execute the reset-brick command (do I have to set debug for the the nodes too?)You have to set the log level to debug for glusterd instance where the commit fails and share the glusterd log of that particular node.
Ok, done.
Command executed on ovirt01 with timestamp "2017-07-06 13:04:12" in glusterd log files
[root@ovirt01 export]# gluster volume reset-brick export gl01.localdomain.local:/gluster/brick3/export start
volume reset-brick: success: reset-brick start operation successful
[root@ovirt01 export]# gluster volume reset-brick export gl01.localdomain.local:/gluster/brick3/export ovirt01.localdomain.local:/gluster/brick3/export commit force
volume reset-brick: failed: Commit failed on ovirt02.localdomain.local. Please check log file for details.
Commit failed on ovirt03.localdomain.local. Please check log file for details.
[root@ovirt01 export]#
See glusterd log files for the 3 nodes in debug mode here:
HIH debugging
Gianluca
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
