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
namespace operation on optane 900P? #346
Comments
If this did support that format, there should have been an 'lbaf' with an 'lbads:12', and then you can select that with an "nvme format /dev/nvmeX -l '. I'm not sure if this one supports 4k or not. The optanes I have do support that, but they're slightly different than the 900P. In any case, if you align IO and partitions to 4k, you should get the same performance out of this as if it were formatted to 4k physical sectors. |
hi Keith, thanks for the explanation
Thanks |
@fengggli if your id-ns only have one lbaf listed, that's means it only support one format. Maybe you should contact your SSD FW vendor for more format support. |
|
I think maybe some enterprise Optane products support extra format. |
@darkbasic Thanks for pointing out. |
Description:
I have a intel 900P installed in a Ubuntu 16.04 machine (with nvme 1.0 kernel module loaded by default)
Some of the system information: (it's recognized as 2700... not 900P, I am not sure it's critical or not..)
I saw the output of the fdisk saying it has 512 byte sector size and i/o size:
My questions:
Is there any way to reformat the nvme to 4k sector size? I am assuming I will achieving better performance instead of using 512 block size.
I have tried the newest release of nvme-format(from the nvme-cli) . using the default configurations(nvme-format + device name) gives the same blocks/sector size. I also tried to delete the default namespaces(nvme detach-ns + nvme delete-ns) and create a new namespace of 4k size (create-ns), but it failed .. some of the output(the operation code sent by nvme-cli somehow is not correct..):
Any comments or suggestions are appreciated!
Thanks
The text was updated successfully, but these errors were encountered: