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

osd/PG: clean up fastinfo key when last_update does not increase #32615

Merged
merged 4 commits into from Jan 15, 2020

Commits on Jan 14, 2020

  1. os/Transaction: add omap_rmkey

    Signed-off-by: Sage Weil <sage@redhat.com>
    liewegas authored and tchaikov committed Jan 14, 2020
    Copy the full SHA
    330e360 View commit details
    Browse the repository at this point in the history
  2. use omap_rmkey() where appropriate

    Signed-off-by: Sage Weil <sage@redhat.com>
    liewegas authored and tchaikov committed Jan 14, 2020
    Copy the full SHA
    bf4177d View commit details
    Browse the repository at this point in the history
  3. crimson: move PG::prepare_write() to .cc file

    less cluttered this way
    
    Signed-off-by: Kefu Chai <kchai@redhat.com>
    tchaikov committed Jan 14, 2020
    Copy the full SHA
    95f28bd View commit details
    Browse the repository at this point in the history
  4. osd/PG: clean up fastinfo key when last_update does not increase

    If the last_update field goes backwards, we write a full info instead of
    the fastinfo key. However, a stale fastinfo key may still be present, and
    it may have a last_update that looks valid to a restarting OSD.
    
    Fixes: https://tracker.ceph.com/issues/43580
    Reported-by: song <jinglesong0814@163.com>
    Signed-off-by: Sage Weil <sage@redhat.com>
    liewegas authored and tchaikov committed Jan 14, 2020
    Copy the full SHA
    3266786 View commit details
    Browse the repository at this point in the history