[Bugs] [Bug 1699866] I/O error on writes to a disperse volume when replace-brick is executed

[bugzilla at redhat.com]

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

Xavi Hernandez <jahernan at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|bugs at gluster.org            |jahernan at redhat.com



--- Comment #1 from Xavi Hernandez <jahernan at redhat.com> ---
The problem happens because a reopen is attempted on all available bricks and
any error it finds is propagated to the main fop.

Basically, when a write fop is sent and ec discovers that there's a brick that
has come up again but doesn't have the fd open, it tries to open it. It could
happen that the file was created when the brick was down and self-heal has not
yet recovered it. In this case the open will fail with ENOENT. This should be
ok, since the other bricks are perfectly fine to successfully process the write
with enough quorum, but this error is not ignored and it's propagated to the
main fop, causing it to fail even before attempting the write.

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