[Bugs] [Bug 1181048] lockless lookup cause disk to be kicked out

[bugzilla at redhat.com]

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

Xavier Hernandez <xhernandez at datalab.es> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED



--- Comment #1 from Xavier Hernandez <xhernandez at datalab.es> ---
I've repeated your test and all bricks are healthy after several iterations.
What error do you get ?

Do you say that some brick is bad only based on the log contents ? if so, these
logs are normal when a regular lookup is made while another operation that
modifies the file is taking place. The root cause of this is that initial
lookups are made asynchronously without any lock taken to all bricks, and since
these bricks are being modified, it could receive inconsistent data that it
shows as a warning. When self-heal checks the file, it sees there's nothing bad
an does nothing.

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