#3 Rasdaemon - disk_error tracepoint error
Opened by djohansen. Modified

This ticket tracks this issue on the SIG side. We are tracking this internally, and a few issues exist already on github.

The issues we are targeting to address:
https://github.com/mchehab/rasdaemon/issues/10
https://github.com/mchehab/rasdaemon/issues/17

Rasdaemon logs disk errors coming from sector 0:0 with no other information, due to an issue with the tracepoint that it uses.

356496 2020-04-05 18:33:16 +0200 error: dev=0:0, sector=-1, nr_sector=0, error='I/O error', rwbs='N', cmd='',

One of our engineers attempted to fix this in https://lkml.org/lkml/2020/1/10/1029, but this was never completed and merged in.

We will be addressing this issue internally and pushing the patches up once validated, and finally build the updated version here.


Metadata Update from @djohansen:
- Issue tagged with: rasdaemon

Metadata Update from @djohansen:
- Custom field Upstream issue adjusted to https://github.com/mchehab/rasdaemon/issues/10

Metadata Update from @ngompa:
- Issue tagged with: c8s

Metadata