Actions
Bug #40204
closedrgw_file: all directories are virtual with respect to contents, and are always invalid
% Done:
0%
Source:
Tags:
Backport:
nautilus, mimic, luminous
Regression:
No
Severity:
3 - minor
Reviewed:
Description
Even materialized directories should be regarded as placeholders only for the names, we cannot trust their mtime for entry caching. To avoid namespace timeouts, moreover, we should introduce at least the option to treat directories as always invalid after a short time period.
Updated by Matt Benjamin almost 5 years ago
- Assignee set to Matt Benjamin
- Pull request ID set to 28451
Updated by Matt Benjamin almost 5 years ago
- Backport set to nautilus, mimic, luminous
Updated by Matt Benjamin almost 5 years ago
- Status changed from New to Fix Under Review
Updated by Matt Benjamin almost 5 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler almost 5 years ago
- Copied to Backport #40262: mimic: rgw_file: all directories are virtual with respect to contents, and are always invalid added
Updated by Nathan Cutler almost 5 years ago
- Copied to Backport #40263: nautilus: rgw_file: all directories are virtual with respect to contents, and are always invalid added
Updated by Nathan Cutler almost 5 years ago
- Copied to Backport #40264: luminous: rgw_file: all directories are virtual with respect to contents, and are always invalid added
Updated by Nathan Cutler about 3 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Actions