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.

Sign up for GitHub

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

Jump to bottom

os/bluestore/BlueFS: use StupidAllocator; fix async compaction bug #11087

Merged
merged 4 commits into from Sep 15, 2016
Merged

os/bluestore/BlueFS: use StupidAllocator; fix async compaction bug #11087

merged 4 commits into from Sep 15, 2016

Commits on Sep 14, 2016

  1. os/bluestore/BlueFS: config option for allocator (default stupid) 

    StupidAllocator is probably a more appropriate choice for bluefs.
Either way, it needn't be tied to what BlueStore is using.

Signed-off-by: Sage Weil <sage@redhat.com>
    @liewegas
    liewegas committed Sep 14, 2016
    Copy the full SHA
    5ef725d View commit details
    Browse the repository at this point in the history

  2. os/bluestore/StupidAllocator: use hex for debug 

    Signed-off-by: Sage Weil <sage@redhat.com>
    @liewegas
    liewegas committed Sep 14, 2016
    Copy the full SHA
    92c5682 View commit details
    Browse the repository at this point in the history

  3. os/bluestore/BlueFS: do not dirty compacting log ino 0 

    Signed-off-by: Sage Weil <sage@redhat.com>
    @liewegas
    liewegas committed Sep 14, 2016
    Copy the full SHA
    7c1a784 View commit details
    Browse the repository at this point in the history

  4. os/bluestore/BlueFS: add safety checks on ino 0|1 op_file_update 

    We only want to log updates on ino 1 in very specific
cases, and never on ino 0.

Signed-off-by: Sage Weil <sage@redhat.com>
    @liewegas
    liewegas committed Sep 14, 2016
    Copy the full SHA
    3759e96 View commit details
    Browse the repository at this point in the history