Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mds: just wait the client flushes the snap and dirty buffer #53238

Merged
merged 1 commit into from Jan 18, 2024

Commits on Nov 15, 2023

  1. mds: just wait the client flushes the snap and dirty buffer

    When truncating the inode we will just set the ifile lock state to
    LOCK_XLOCKSNAP and then try to revoke the 'Fb' caps, but if the
    client couldn't release the 'Fb' cap in time just replies with a
    normal cap updating request, the MDS will successfully transfer
    the ifile's lock state to LOCK_EXCL, which is stable.
    
    That means the MDS will wake up the truncating request and continue
    truncating the objects from Rados without waiting the clients to
    flush the diry buffer.
    
    Fixes: commit 9c65920 ("mds: force client flush snap data before
    		truncating objects")
    Fixes: https://tracker.ceph.com/issues/62580
    Signed-off-by: Xiubo Li <xiubli@redhat.com>
    lxbsz committed Nov 15, 2023
    Configuration menu
    Copy the full SHA
    68179ae View commit details
    Browse the repository at this point in the history