Re: NVMe support with 6.5

Thank you for your reply.




> Smartctl should possibly indicate that these fields are not set instead 
> of printing "0 [0 B]".

Indeed if the capacity field could state something like "not defined", that would make things more clear for the user.




> This should print [1.5x TB] because a unit is 1000*512 bytes. This is 
> now fixed in r4293.

Tested, great !



A last question, command "smartctl -t short /dev/nvme0" gives result:

NVMe device successfully opened



I am not aware if NVMe drive manufacturers include selftests, but in the case they don't, a message like "not supported" would be nice to have so.



Looking out for 6.5 release, great work :)



Regards,

Ozy.



-----Message initial-----
De: Christian Franke <[email protected]>
Envoyé: jeudi 14 avril 2016 22:05
À: Ozy de Jong <[email protected]>
Cc: [email protected]
Sujet: Re: [smartmontools-support] NVMe support with 6.5


Ozy de Jong wrote:
> NVMe support with 6.5
>
> Hello,
>
>
> I'm testing smartmontools-6.5-0-20160413-r4292.linux-x86_64 on a 
> Samsung 950 Pro SSD and get incorrect output I guess.
>

Thanks for testing!


> The Total NVM Capacity is hopefully not 0 B, and the Temp.
>

The capacity fields are optional for devices with only 1 namespace.

NVMe 1.2a: "This field shall be supported if Namespace Management and 
Namespace Attachment commands are supported."

Smartctl should possibly indicate that these fields are not set instead 
of printing "0 [0 B]".


> Thresholds aren't read either.
>

NVMe 1.2a: "A value of 0h in this field indicates that no ... 
temperature threshold value is reported by the controller."

smartctl prints '-' for the then instead of 0 Kelvin or -273 Celsius.



> [root@badcore9 sbin] # ./smartctl -a /dev/nvme0
> smartctl 6.5 2016-04-12 r4292 [x86_64-linux-4.4.6-301.fc23.x86_64] 
> (daily-20160413)
> ...
> Total NVM Capacity:                 0 [0 B]
> Unallocated NVM Capacity:           0 [0 B]
> ...
> Number of Namespaces:               1
> ...
> Warning  Comp. Temp. Threshold:     -
> Critical Comp. Temp. Threshold:     -


There is actually one minor bug:

> Data Units Read:                    2 951 361 [1,51 GB]
> Data Units Written:                 2 983 067 [1,52 GB]
>

This should print [1.5x TB] because a unit is 1000*512 bytes. This is 
now fixed in r4293.

Thanks,
Christian


------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Smartmontools-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/smartmontools-support

------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z

_______________________________________________
Smartmontools-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/smartmontools-support