with 4dht cluster setup ,fuse mounted it client and did untar kernel. while untar is running - tried replace-brick (replace brick4 with new brick5) it succeeded but on untar on client fails. fuse log file can be found /share/tickets/2107
Did not hit this bug in my setup. Tried it twice with 3.1.2. I think I did see some "No such file or directory" errors, but tar continued without any further issues. Are you referring to these error messages as failures? The way I did it was to run untar on the mount point (fuse mount) and then performed - gluster volume replace-brick testvol <brick_current> <brick_new> start gluster volume replace-brick testvol <brick_current> <brick_new> commit Which log file are you referring to as "fuse log file" ? I looked at all the files in /usr/local/var/log/glusterfs and there doesn't seem to be one under that name.
Can you please respond to the update?
(In reply to comment #1) > Did not hit this bug in my setup. Tried it twice with 3.1.2. > I think I did see some "No such file or directory" errors, but tar continued > without any further issues. On client it displayed mesg like "No such file or directory" but untar operation failed with mesg like "tar failed due to previous errors " > > Which log file are you referring to as "fuse log file" ? I looked at all the > files in /usr/local/var/log/glusterfs and there doesn't seem to be one under > that name. I was referring to glusterfs client log file. (/usr/local/var/log/glusterfs/<mnt-pt>.log)
Can you please check it with 3.1.2 and let me know if you still hit the issue ? (As mentioned in the previous update, my experiment did not hit the issue).
*** This bug has been marked as a duplicate of bug 1812 ***