Details
-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
None
-
3
-
9223372036854775807
Description
In ll_md_blocking_ast(), we zero all timestamps to avoid these 'leftovers' interfering the new timestamps from MDS, especially when the timestamps are set back by other clients. It's not quite right to change timestamps in this way, because:
1. The pending lock can be matched by getattr, so these zero timestamps can be fetched by application in a small race window.
2. It doesn't make sense to zero the mtime and ctime, because we always use the newest ctime and mtime from MDS when do attributes merge, the 'leftovers' won't interfere new timestamps set by other clients.
Attachments
Activity
| Link | New: This issue is related to JNET-40 [ JNET-40 ] |
| Link | New: This issue is related to LDEV-567 [ LDEV-567 ] |
| Link | New: This issue is related to LDEV-341 [ LDEV-341 ] |
| Link | New: This issue is related to LDEV-367 [ LDEV-367 ] |
| Link | New: This issue is related to LDEV-243 [ LDEV-243 ] |
| Link | New: This issue is related to LDEV-301 [ LDEV-301 ] |
| Link | Original: This issue is related to JFC-19 [ JFC-19 ] |
| Fix Version/s | New: Lustre 2.10.0 [ 12204 ] | |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
| Link | New: This issue is related to JFC-19 [ JFC-19 ] |
| Link | New: This issue is related to JFC-17 [ JFC-17 ] |