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

nvme device offset calculation can be wrong #188

Open

JeffreyDevloo opened this issue Sep 14, 2018 · 1 comment

Assignees

Labels

state_codecomplete type_bug

Milestone

Contributor

JeffreyDevloo commented Sep 14, 2018

Seen on a nuvolat environment. The starting block was way higher than anticipated and it calculated the offset to being 1.5tb on a 1.4tb drive

We should use parted instead of fetching the starting block

JeffreyDevloo self-assigned this

JeffreyDevloo added the state_inprogress label

wimpers added this to the N milestone

wimpers added the type_bug label

Contributor Author

JeffreyDevloo commented Oct 16, 2018

Fixed by #189

JeffreyDevloo added state_codecomplete and removed state_inprogress labels

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment