client: fire the finish_cap_snap() after buffer being flushed#38732
client: fire the finish_cap_snap() after buffer being flushed#38732batrick merged 4 commits intoceph:masterfrom
Conversation
09008c8 to
859c364
Compare
|
jenkins test make check |
batrick
left a comment
There was a problem hiding this comment.
Otherwise LGTM. Thanks for tracking that down!
a6d3d64 to
616084c
Compare
|
jenkins test api |
|
New failures are: New failures are related to snaps. I fear this PR may be the cause. |
Signed-off-by: Xiubo Li <xiubli@redhat.com>
Signed-off-by: Xiubo Li <xiubli@redhat.com>
Signed-off-by: Xiubo Li <xiubli@redhat.com>
When the inode has Fb cap and the used reference is none zero, the cap snap flushing will be delayed, so we need to make sure it will be invoked after the dirty buffer is flushed to osd. Fixes: https://tracker.ceph.com/issues/48679 Signed-off-by: Xiubo Li <xiubli@redhat.com>
616084c to
a34d0c2
Compare
I think I fogot to clean the |
|
@batrick Fixed it, PTAL. Thanks. |
@batrick |
|
The new issue https://tracker.ceph.com/issues/49928 is also caused by this bug. I think the old code want to call the |
|
ACK, thanks for checking htat |
|
|
This change looks good/safe to me so I'm merging it. We did have this new failure come up but I don't think it's related, so far: https://tracker.ceph.com/issues/50021 Please have a look though. |
Sure, will check it. |
When the inode has Fb cap and the used reference is none zero, the
cap snap flushing will be delayed, so we need to make sure it will
be invoked after the dirty buffer is flushed to osd.
Fixes: https://tracker.ceph.com/issues/48679
Signed-off-by: Xiubo Li xiubli@redhat.com
Checklist
Show available Jenkins commands
jenkins retest this pleasejenkins test classic perfjenkins test crimson perfjenkins test signedjenkins test make checkjenkins test make check arm64jenkins test submodulesjenkins test dashboardjenkins test apijenkins test docsjenkins render docsjenkins test ceph-volume alljenkins test ceph-volume tox