Opened 5 weeks ago

Last modified 4 weeks ago

#1463 new defect

Samsung NVME Power on Hours: - space between the digits of the value

Reported by: Anna Maj Owned by:
Priority: minor Milestone: undecided
Component: smartctl Version: 7.2
Keywords: nvme Cc:


smartctl - in the case of samsung nvme disks for values ​​above 1000h, the returned Power of Hours: 1 234 always contains a space between the first and second digit

for other disks everything is fine ( Power of Hours: 1234 )


Change History (4)

comment:1 Changed 5 weeks ago by TheDragonFire961

I don't think we'll be able to get anywhere without evidence of the bug. Do you have a smartctl printout demonstrating the POH behaviour? A model number of the SSD that causes the bug would also be helpful.

Last edited 5 weeks ago by TheDragonFire961 (previous) (diff)

comment:2 Changed 5 weeks ago by Christian Franke

Keywords: nvme added; Samsung NVME Power on Hours: removed
Type: patchdefect

Please be more specific and provide a sample output. Redirect smartctl output to a file and attach(!) the file to this ticket. Do NOT cut and paste from console or to a ticket comment.

Which locale is configured (e.g. output of locale command) ?

Smartctl NVMe attribute output uses localized digit grouping. Retry with a different locale (e.g. change environment variables LANG or LC_NUMERIC).

comment:3 Changed 4 weeks ago by TheDragonFire961

Think we should be downgrading this to minor or maybe even trivial priority. What's being described seems to be little more than a visual glitch (or not even that, some do prefer a space as their thousands separator).

Last edited 4 weeks ago by TheDragonFire961 (previous) (diff)

comment:4 Changed 4 weeks ago by Christian Franke

Priority: majorminor

It is very likely a locale issue:
For example with LANG=pl_PL.utf-8 or LANG=ru_RU.utf-8 (or same LC_NUMERIC=...), the thousands_sep string is "\xc2\xa0". This is U+00A0 (NBSP) which is printed as space.

Workaround for POSIX systems: Run smartctl with LANG=, LANG=C, LANG=POSIX, ...

PS: The ticket priority is negligible if milestone is still undecided.

Note: See TracTickets for help on using tickets.