On Thursday 05 March 2015 15.50:12 Stanislav Brabec wrote:
Bruno Friedmann wrote:
On Wednesday 04 March 2015 23.30:09 Yamaban wrote:
On Wed, 4 Mar 2015 22:41, Stanislav Brabec wrote: +1, maybe as the last of 'cron.daily' or what-ever systemd calls that now. +1, also as last of 'cron.monthly'
Not from cron. smartd itself has this capability. It is configured in /etc/smartd.conf. It starts it with delays, and check, whether the last check already finished.
In that case no problems, I was thinking the idea was a /etc/cron.*/thing
Is it really the best way? If you have a whatever storage computer with lot of disk and there's a running backup at that time, it will kill all the io bandwidth.
This should not kill I/O bandwidth. Firmware should postpone the check until the device is idle.
The mention of that "behaviour for some" "bug for some other" will be hard to detect no?
It would not be our bug, but HDD manufacturers' bug. The last report about such bug in our Bugzilla is dated
People will still have a chance to: - Upgrade HDD firmware - Notify HDD manufacturer about this problem. - Turn S.M.A.R.T. checks off. - Run checks manually when the system is idle.
Well, I can imagine a test, that can detect broken firmware: 1. Start some I/O. 2. Start self test. 3. Start the same I/O as 1. did.
If there is a big difference in speed, report bad firmware. Oh that is not always useful, I know a numerous bad firmware of WD harddrive, that WD doesn't want to offer a way to upgrade them. (Not high end hdd sas)
I guess that most real admin in charge of server/dekstop knows the perfect time to run full deep long test. We will impose 2 actions, remove default scripts and install theirs.
S.M.A.R.T. checks are fully configurable by /etc/smartd.conf.
Are people aware that S.M.A.R.T. is configured to an inferior mode and cannot predict many failures?
What is better? Risk slow down on some devices (and people no being aware of it source) or risk disk death that can be predicted but it is not (because self tests are not started)? Nope having smartd running is perfect, (I'm fan boy of it and doesn't have trouble with since 10 years) Still I'm not sure that casual Joe will see the log in time or inside smartd package we will have a kinda script able to wall everybody connected or desktop notification. (Mail warning are more used by experienced admins)
And what about smartd and udisk2 doing the same work? On most desktop udiskd2 is running and already doing smart check status ?
smartd is a hardware monitor that communicates with firmware using special commands. Disk health monitoring is the only purpose of smartd. It never reads any data from the disk.
udisks2 is a standard block device manager. It does not any health checks. Then why it is shouting when you remove a removable device from system for example? déc 28 11:04:40 yoda udisksd[5446]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/SAMSUNG_HD501LJ_S0MUJ1PP431740: Error updating SMART data: sk_disk_open: No such file or directory (seems to be related to https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1281588/comments/29)
And as the doc also refer it http://udisks.freedesktop.org/docs/1.91.0/gdbus-org.freedesktop.UDisks2.Driv... I'm still asking myself if it doesn't create a double check with smartd activated. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Board, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org