[Bugs] [Bug 1361518] Files not able to heal after arbiter and data bricks were rebooted

[bugzilla at redhat.com]

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

Ravishankar N <ravishankar at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Doc Type|If docs needed, set a value |Known Issue


--- Doc Text *updated* ---
Problem:
If a file create is wound to all bricks, and the FOP succeeds only on arbiter, the application will get a failure, but during self-heal conservative merge, the zero byte file gets created on the data bricks with arbiter marked as source. Since data self-heal can never happen from arbiter, 'heal-info' will list the entries forever.

Workaround:
If 'gluster vol heal <volname> info` shows pending data heals for a file which is zero byte size on all bricks, it should be safe to delete the file from the mount, subsequent to which the file should also no longer appear in heal-info output.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=gTdHWVLIcS&a=cc_unsubscribe