[Bugs] [Bug 1410425] [GNFS+EC] Cthon failures/issues with Lock/ Special Test cases on disperse volume with GNFS mount

[bugzilla at redhat.com]

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



--- Comment #5 from Pranith Kumar K <pkarampu at redhat.com> ---
(In reply to Xavier Hernandez from comment #4)
> Mandatory locks will need some additional work.
> 
> If mandatory locks are handled by the features/locks xlator, it will need
> some additional info for each write to know the real offset/length of each
> write. Otherwise I don't see a way to allow a fine grained mandatory lock
> support for ec.

Yay! I was thinking of passing that in xdata as well. Okay for now let's send
this off, we can work on that as part of another bug. Only other bug I saw is
doing dispatch_all for nonblocking locks. Posix locks does this lock merging
etc right, so when we lock and unlock it may truncate the lock range.

i.e. If we already have a lock from 0-10 and then we do a lock for 5-15 by same
fd/owner it will become a single lock 0-15. Now if we do unlock from 5-15
because some other node hit EAGAIN because a parallel conflicting lock on say
range 11-12. Then the resulting unlock on 5-15 will lead to 0-5

In afr it is always wound incrementally one node after the other.

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