https://bugs.kde.org/show_bug.cgi?id=491401
Bug ID: 491401
Summary: SMART notification reporting is delayed
Classification: Plasma
Product: plasma-disks
Version: unspecified
Platform: Debian testing
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: bugs.kde....@zetafleet.com
CC: sit...@kde.org
Target Milestone: ---
SUMMARY
My system experienced a disk hardware failure. The disk fell off the bus and
then came back after a reboot with SMART failed status. smartd noticed this
immediately and triggered its own reporting mechanism, and now emits critical
errors to syslog every 30 minutes. plasma-disks took a whole day to notice that
there was a SMART error and raise a notification.
Glancing at the source code for plasma-disks, it does look like there is a
fixed 24-hour timer in there to scan devices, so I guess that is probably how
it finally managed to trigger a check and notify. Restarting the plasma-disks
service causes it to report immediately, so I am not sure why it did not
trigger on reboot, since the failing device already had to be initialised and
on the bus for the system to even boot that far.
STEPS TO REPRODUCE
1. Experience a hardware vendor trying to ruin your day
OBSERVED RESULT
No notification from the OS
EXPECTED RESULT
plasma-disks notifies immediately (or at least shortly thereafter) about the
failure
SOFTWARE/OS VERSIONS
Operating System: Debian GNU/Linux 12
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.13
Kernel Version: 6.9.10-amd64 (64-bit)
ADDITIONAL INFORMATION
If that 24 hour timer indeed is the only thing doing re-checks, and there is no
easy way or desire to use smartd, it seems like it would be trivial and
advisable to reduce the check time to something like 30 minutes.
--
You are receiving this mail because:
You are watching all bug changes.
