Quantcast
Channel: Intel Communities : All Content - Solid State Drives
Viewing all articles
Browse latest Browse all 3689

set sector/block size in 900P in ubuntu.

$
0
0

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..)

lifeng@1wk300(x-pheonix:2):~/Workspace/x-phoenix/build$lspci |tail -1

04:00.0 Non-Volatile memory controller: Intel Corporation Device 2700

lifeng@1wk300(x-pheonix:2):~/Workspace/x-phoenix/build$uname -a

Linux 1wk300 4.13.0-38-generic #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

 

 

However I saw the output of the fdisk saying it has 512 byte sector size and i/o size

Disk /dev/nvme0n1: 260.9 GiB, 280065171456 bytes, 547002288 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes 

So here are some of my questions and doubts:

 

1. 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.

2. 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 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..):

lifeng@1wk300(x-pheonix:2):~/Workspace/x-phoenix/build$sudo nvme detach-ns /dev/nvme0 --namespace-id=0x1

NVMe Status:INVALID_OPCODE(4001)

 

lifeng@1wk300(x-pheonix:2):~/Workspace/x-phoenix/build$sudo nvme list-ns /dev/nvme0 --namespace-id=0x1

[   0]:0x209a97b0

[   2]:0x209a97b0

[   4]:0x209a97b0

[  32]:0x2090000

lifeng@1wk300(x-pheonix:2):~/Workspace/x-phoenix/build$sudo nvme list-ns /dev/nvme0

NVMe Status:INVALID_NS(400b) NSID:0

lifeng@1wk300(x-pheonix:2):~/Workspace/x-phoenix/build$sudo nvme id-ns /dev/nvme0 --namespace-id=0x1

NVME Identify Namespace 1:

nsze    : 0x209a97b0

ncap    : 0x209a97b0

nuse    : 0x209a97b0

nsfeat  : 0

nlbaf   : 0

flbas   : 0

mc      : 0

dpc     : 0

dps     : 0

nmic    : 0

rescap  : 0

fpi     : 0

nawun   : 0

nawupf  : 0

nacwu   : 0

nabsn   : 0

nabo    : 0

nabspf  : 0

noiob   : 0

nvmcap  : 0

nguid   : 00000000000000000000000000000000

eui64   : 0000000000000000

lbaf  0 : ms:0   lbads:9  rp:0x2 (in use)

 

3. I saw someone suggest using intel ssd data center tool. but it seems like it cannot recognize this ssd... perhaps this product is not supported yet?

lifeng@1wk300(x-pheonix:2):~/Workspace/x-phoenix/build$sudo isdct show -a -intelssd

 

No results

 

 

Thanks!


Viewing all articles
Browse latest Browse all 3689

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>