Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #79898
| From | Daniel Swarbrick <dswarbrick@debian.org> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#1041745: smartd[…]: Device: /dev/nvme0, number of Error Log entries increased from … to … |
| Date | 2023-08-02 21:20 +0200 |
| Message-ID | <GYpy1-4EXO-1@gated-at.bofh.it> (permalink) |
| References | <GUuPD-24Zn-1@gated-at.bofh.it> <GUuPD-24Zn-1@gated-at.bofh.it> <GUuPD-24Zn-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
[Multipart message — attachments visible in raw view] - view raw
This sounds quite similar to this: https://github.com/linux-nvme/libnvme/issues/550 Even prior to that bug, I noticed that the smart error log counter would increment by one with every reboot. This was not too concerning, but when nvme-cli 2.x started to result in (albeit innocent) errors being logged each time a "nvme list" command was executed, it became an annoyance. As I understand it, it was due to the SSD being fairly old, and the firmware only supporting a fairly outdated version of the NVMe spec (< 1.2) At least the _kernel_ should have fixed this, with commit https://github.com/torvalds/linux/commit/d7ac8dca938cd60cf7bd9a89a229a173c6bcba87 A fix for nvme-cli (via libnvme) is still being worked on, AFAIK.
Back to linux.debian.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
Bug#1041745: smartd[…]: Device: /dev/nvme0, number of Error Log entries increased from … to … Daniel Swarbrick <dswarbrick@debian.org> - 2023-08-02 21:20 +0200 Bug#1041745: smartd[…]: Device: /dev/nvme0, number of Error Log entries increased from … to … "Al Ma" <alma0@ro.ru> - 2023-08-04 02:20 +0200
csiph-web