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

os/bluestore: fix when block device is not a multiple of the block size #10844

Merged
4 commits merged into from Aug 26, 2016

Conversation

liewegas
Copy link
Member

Also fsck after mkfs by default.

Signed-off-by: Sage Weil <sage@redhat.com>
Signed-off-by: Sage Weil <sage@redhat.com>
We might have a backing device that is an odd number of 512-byte sectors
but have the block_size configured to 4096.  Ensure the reported size
rounds down to avoid confusing other layers of the stack.

Signed-off-by: Sage Weil <sage@redhat.com>
@ghost ghost self-assigned this Aug 24, 2016
@ghost
Copy link

ghost commented Aug 24, 2016

jenkins test this please

@ghost
Copy link

ghost commented Aug 25, 2016

2016-08-24 20:44:53.774324 7f50eff8a040  1 bluefs add_block_extent bdev 1 0x100000~7efce00
/home/jenkins-build/build/workspace/ceph-pull-requests/src/os/bluestore/BlueFS.cc: In function 'void BlueFS::add_block_extent(unsigned int, uint64_t, uint64_t)' thread 7f50eff8a040 time 2016-08-24 20:44:53.774333
/home/jenkins-build/build/workspace/ceph-pull-requests/src/os/bluestore/BlueFS.cc: 138: FAILED assert(bdev[id]->get_size() >= offset + length)

jenkins test this please because we want to make sure it is because of this pull request

These should be a multiple of the block size (since we are feeding
the size directly into add_block_extent).

Signed-off-by: Sage Weil <sage@redhat.com>
@liewegas
Copy link
Member Author

Fixed!

@ghost ghost merged commit b0ae9df into ceph:master Aug 26, 2016
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant