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

bdev sector size should default to a value that is more widely acceptable #224

Closed
pcuzner opened this issue Sep 6, 2023 · 0 comments · Fixed by #234
Closed

bdev sector size should default to a value that is more widely acceptable #224

pcuzner opened this issue Sep 6, 2023 · 0 comments · Fixed by #234
Assignees

Comments

@pcuzner
Copy link
Contributor

pcuzner commented Sep 6, 2023

When a bdev is created it defaults to a 4kn sector size, but this is not compatible with platforms like vmware. When vmware encounters a device at 4kn, it simple doesn't show up in the UI - no error messages. To diagnose you must look at vmkernel.log to determine the reason why the device was rejected - which is not a great experience for someone just trialing the gateway and ceph.

I'd propose a default of 512, so these issues aren't hit

Tasks

No tasks being tracked yet.
@gbregman gbregman self-assigned this Sep 14, 2023
gbregman added a commit to gbregman/ceph-nvmeof that referenced this issue Sep 18, 2023
Fixes ceph#224

Signed-off-by: Gil Bregman <gbregman@il.ibm.com>
gbregman added a commit to gbregman/ceph-nvmeof that referenced this issue Sep 18, 2023
Fixes ceph#224

Signed-off-by: Gil Bregman <gbregman@il.ibm.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants