Opened 4 years ago
Closed 19 months ago
#1463 closed defect (invalid)
Samsung NVME Power on Hours: - space between the digits of the value
Reported by: | Anna Maj | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | smartctl | Version: | 7.2 |
Keywords: | nvme | Cc: |
Description
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 )
greetings
Anna
Change History (5)
comment:2 by , 4 years ago
Keywords: | nvme added; Samsung NVME Power on Hours: removed |
---|---|
Type: | patch → defect |
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 by , 4 years ago
Think we should be downgrading this to minor 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).
comment:4 by , 4 years ago
Priority: | major → minor |
---|
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.
comment:5 by , 19 months ago
Milestone: | undecided |
---|---|
Resolution: | → invalid |
Status: | new → closed |
This is likely a locale issue. No feedback from reporter.
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.