On Wednesday 04 March 2015 23.30:09 Yamaban wrote:
On Wed, 4 Mar 2015 22:41, Stanislav Brabec wrote:
Hallo.
Many years ago we decided that smartd will not enable self tests by default.
[snip reasons]
Short Self Test: Short Self Test verifies status of the hardware function. It takes several minutes.
I propose to run Short Self Test once a day.
+1, maybe as the last of 'cron.daily' or what-ever systemd calls that now.
...
Long Self Test: Long Self Test (nearly for sure) performs full surface scan. It typically takes several to many hours. ... I propose to run Long Self Test once a month.
+1, also as last of 'cron.monthly'
Thank you for bringing this up to general notice.
- Yamaban
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. The mention of that "behaviour for some" "bug for some other" will be hard to detect no? 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. And what about smartd and udisk2 doing the same work? On most desktop udiskd2 is running and already doing smart check status ? -- 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