Details
-
Improvement
-
Resolution: Unresolved
-
Trivial
-
None
-
Lustre 2.5.0
-
None
-
9399
Description
When OI scrub try to recover the OST-objects under /lost+found, it may meet the case that the OI mapping slot in /O/<seq>/d<x> has been reused by others. The new OST-object may have been modified by others already, and may be not. For the later case (zero-sized and with SUID+SGID), we want to remove it and insert the original one back to the /O/<seq>/d<x>. But there are something to be considered:
1) The OST-object under /lost+found has crashed LMA. So it should not conflict with the current one.
2) There are race conditions that: someone may just want to modify the current one. Even if the OI scrub takes the object lock when remove the current one, it still cause the modification to be lost becasue the target
has been removed when the RPC service thread waiting for the lock.