[Bugs] [Bug 1431955] [Disperse] Implement open fd heal for disperse volume

[bugzilla at redhat.com]

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

Pranith Kumar K <pkarampu at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pkarampu at redhat.com



--- Comment #1 from Pranith Kumar K <pkarampu at redhat.com> ---
Sunil,
   When you do a dd on a file and as long as the file is open, you see
something like the following in statedump of the client:

[xlator.protocol.client.ec2-client-0.priv]
fd.0.remote_fd=0
connecting=0
connected=1
total_bytes_read=7288220
ping_timeout=42
total_bytes_written=11045016
ping_msgs_sent=3
msgs_sent=19812

This should be present for each of the fds that are open from each
client-xlator.
So if we have 3=2+1 configuration we will have one for each of the client
xlators. But if the brick was down at the time of opening the file this won't
be present. Now after bringing the brick back up and operating on the file we
should have this file opened again. I think at the moment this gets converted
to anonymous-fd based operation so the operation may not fail. But it is
important to open the file again for all operations to function properly like
lk etc.

-- 
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=Hv8uYvzOGb&a=cc_unsubscribe