Bug #52123
closed
mds sends cap updates with btime zeroed out
Added by Jeff Layton almost 3 years ago.
Updated almost 2 years ago.
Description
The MDS is sending cap updates that have the btime zeroed out in some cases. Ensure that it's sending the right btime, every time.
- Pull request ID set to 42737
This was noticed as I was replicating the problem in #46574. With this PR in place, the btime is correctly reported in that scenario. The mtime problem in that bug is a separate issue, however.
- Status changed from New to Fix Under Review
- Target version set to v17.0.0
- Source set to Development
- Backport set to pacific,octopus
- Component(FS) MDS added
- Status changed from Fix Under Review to Pending Backport
- Copied to Backport #52634: octopus: mds sends cap updates with btime zeroed out added
- Copied to Backport #52635: pacific: mds sends cap updates with btime zeroed out added
- Assignee changed from Jeff Layton to Venky Shankar
Not sure what has to happen to unwedge this backport.
- Tags set to backport_processed
- Status changed from Pending Backport to Resolved
- Tags deleted (
backport_processed)
Also available in: Atom
PDF