smartmontools - Is the automatic test the same as running a short test?
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
We're busy setting up smartmontools on our various Linux based servers and although it works, we want to streamline the process a bit. As I understand, we can enable automatic testing which should perform a test each 4 hours, but it does not indicate exactly what test is completed?
Is this test the same as running a short test? We're currently manually doing short tests daily so if the automatic test done each 4 hours is the same I would rather just rely on the automatic testing.
centos smartctl smart smartmontools
add a comment |Â
up vote
0
down vote
favorite
We're busy setting up smartmontools on our various Linux based servers and although it works, we want to streamline the process a bit. As I understand, we can enable automatic testing which should perform a test each 4 hours, but it does not indicate exactly what test is completed?
Is this test the same as running a short test? We're currently manually doing short tests daily so if the automatic test done each 4 hours is the same I would rather just rely on the automatic testing.
centos smartctl smart smartmontools
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
We're busy setting up smartmontools on our various Linux based servers and although it works, we want to streamline the process a bit. As I understand, we can enable automatic testing which should perform a test each 4 hours, but it does not indicate exactly what test is completed?
Is this test the same as running a short test? We're currently manually doing short tests daily so if the automatic test done each 4 hours is the same I would rather just rely on the automatic testing.
centos smartctl smart smartmontools
We're busy setting up smartmontools on our various Linux based servers and although it works, we want to streamline the process a bit. As I understand, we can enable automatic testing which should perform a test each 4 hours, but it does not indicate exactly what test is completed?
Is this test the same as running a short test? We're currently manually doing short tests daily so if the automatic test done each 4 hours is the same I would rather just rely on the automatic testing.
centos smartctl smart smartmontools
asked Nov 29 '17 at 9:12
mauzilla
1033
1033
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
The short answer is no, these are not equivalent. Automatic testing is just data collection; the short test is an actual test.
This is discussed (at length) in the smartctl
manpage, in the section describing the --offlineauto
settings:
The second category of testing is called "offline" testing. This type of test can, in principle,
degrade the device performance. The-o on
option causes this offline testing to be carried out,
automatically, on a regular scheduled basis. Normally, the disk will suspend offline testing
while disk accesses are taking place, and then automatically resume it when the disk would otherwise be idle, so in practice it has little effect. Note that a one-time offline test can also be
carried out immediately upon receipt of a user command. See the-t offline
option below, which
causes a one-time offline test to be carried out immediately.
and
The third category of testing (and the only category for which the word âÂÂtestingâ is really an
appropriate choice) is "self" testing. This third type of test is only performed (immediately) when a command to run it is issued. The-t
and-X
options can be used to carry out and abort
such self-tests; please see below for further details.
So -t offline
is equivalent to the automatic testing enabled with -o on
, but thatâÂÂs not testing, itâÂÂs just data collection (it updates the âÂÂofflineâ attributes). The short test, scheduled manually (or using smartd
), is an actual test, as is the long test; smartd
comes with example settings enabling nightly short tests and weekly long tests.
Thank you @Stephen, well answered! I've had some issues with smartd.conf not performing the tests so will setup a cronjob that first ensures offline test data is collected, run a manual daily short test and a long test once a month over weekends.
â mauzilla
Nov 29 '17 at 9:29
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
The short answer is no, these are not equivalent. Automatic testing is just data collection; the short test is an actual test.
This is discussed (at length) in the smartctl
manpage, in the section describing the --offlineauto
settings:
The second category of testing is called "offline" testing. This type of test can, in principle,
degrade the device performance. The-o on
option causes this offline testing to be carried out,
automatically, on a regular scheduled basis. Normally, the disk will suspend offline testing
while disk accesses are taking place, and then automatically resume it when the disk would otherwise be idle, so in practice it has little effect. Note that a one-time offline test can also be
carried out immediately upon receipt of a user command. See the-t offline
option below, which
causes a one-time offline test to be carried out immediately.
and
The third category of testing (and the only category for which the word âÂÂtestingâ is really an
appropriate choice) is "self" testing. This third type of test is only performed (immediately) when a command to run it is issued. The-t
and-X
options can be used to carry out and abort
such self-tests; please see below for further details.
So -t offline
is equivalent to the automatic testing enabled with -o on
, but thatâÂÂs not testing, itâÂÂs just data collection (it updates the âÂÂofflineâ attributes). The short test, scheduled manually (or using smartd
), is an actual test, as is the long test; smartd
comes with example settings enabling nightly short tests and weekly long tests.
Thank you @Stephen, well answered! I've had some issues with smartd.conf not performing the tests so will setup a cronjob that first ensures offline test data is collected, run a manual daily short test and a long test once a month over weekends.
â mauzilla
Nov 29 '17 at 9:29
add a comment |Â
up vote
2
down vote
accepted
The short answer is no, these are not equivalent. Automatic testing is just data collection; the short test is an actual test.
This is discussed (at length) in the smartctl
manpage, in the section describing the --offlineauto
settings:
The second category of testing is called "offline" testing. This type of test can, in principle,
degrade the device performance. The-o on
option causes this offline testing to be carried out,
automatically, on a regular scheduled basis. Normally, the disk will suspend offline testing
while disk accesses are taking place, and then automatically resume it when the disk would otherwise be idle, so in practice it has little effect. Note that a one-time offline test can also be
carried out immediately upon receipt of a user command. See the-t offline
option below, which
causes a one-time offline test to be carried out immediately.
and
The third category of testing (and the only category for which the word âÂÂtestingâ is really an
appropriate choice) is "self" testing. This third type of test is only performed (immediately) when a command to run it is issued. The-t
and-X
options can be used to carry out and abort
such self-tests; please see below for further details.
So -t offline
is equivalent to the automatic testing enabled with -o on
, but thatâÂÂs not testing, itâÂÂs just data collection (it updates the âÂÂofflineâ attributes). The short test, scheduled manually (or using smartd
), is an actual test, as is the long test; smartd
comes with example settings enabling nightly short tests and weekly long tests.
Thank you @Stephen, well answered! I've had some issues with smartd.conf not performing the tests so will setup a cronjob that first ensures offline test data is collected, run a manual daily short test and a long test once a month over weekends.
â mauzilla
Nov 29 '17 at 9:29
add a comment |Â
up vote
2
down vote
accepted
up vote
2
down vote
accepted
The short answer is no, these are not equivalent. Automatic testing is just data collection; the short test is an actual test.
This is discussed (at length) in the smartctl
manpage, in the section describing the --offlineauto
settings:
The second category of testing is called "offline" testing. This type of test can, in principle,
degrade the device performance. The-o on
option causes this offline testing to be carried out,
automatically, on a regular scheduled basis. Normally, the disk will suspend offline testing
while disk accesses are taking place, and then automatically resume it when the disk would otherwise be idle, so in practice it has little effect. Note that a one-time offline test can also be
carried out immediately upon receipt of a user command. See the-t offline
option below, which
causes a one-time offline test to be carried out immediately.
and
The third category of testing (and the only category for which the word âÂÂtestingâ is really an
appropriate choice) is "self" testing. This third type of test is only performed (immediately) when a command to run it is issued. The-t
and-X
options can be used to carry out and abort
such self-tests; please see below for further details.
So -t offline
is equivalent to the automatic testing enabled with -o on
, but thatâÂÂs not testing, itâÂÂs just data collection (it updates the âÂÂofflineâ attributes). The short test, scheduled manually (or using smartd
), is an actual test, as is the long test; smartd
comes with example settings enabling nightly short tests and weekly long tests.
The short answer is no, these are not equivalent. Automatic testing is just data collection; the short test is an actual test.
This is discussed (at length) in the smartctl
manpage, in the section describing the --offlineauto
settings:
The second category of testing is called "offline" testing. This type of test can, in principle,
degrade the device performance. The-o on
option causes this offline testing to be carried out,
automatically, on a regular scheduled basis. Normally, the disk will suspend offline testing
while disk accesses are taking place, and then automatically resume it when the disk would otherwise be idle, so in practice it has little effect. Note that a one-time offline test can also be
carried out immediately upon receipt of a user command. See the-t offline
option below, which
causes a one-time offline test to be carried out immediately.
and
The third category of testing (and the only category for which the word âÂÂtestingâ is really an
appropriate choice) is "self" testing. This third type of test is only performed (immediately) when a command to run it is issued. The-t
and-X
options can be used to carry out and abort
such self-tests; please see below for further details.
So -t offline
is equivalent to the automatic testing enabled with -o on
, but thatâÂÂs not testing, itâÂÂs just data collection (it updates the âÂÂofflineâ attributes). The short test, scheduled manually (or using smartd
), is an actual test, as is the long test; smartd
comes with example settings enabling nightly short tests and weekly long tests.
answered Nov 29 '17 at 9:25
Stephen Kitt
143k22311377
143k22311377
Thank you @Stephen, well answered! I've had some issues with smartd.conf not performing the tests so will setup a cronjob that first ensures offline test data is collected, run a manual daily short test and a long test once a month over weekends.
â mauzilla
Nov 29 '17 at 9:29
add a comment |Â
Thank you @Stephen, well answered! I've had some issues with smartd.conf not performing the tests so will setup a cronjob that first ensures offline test data is collected, run a manual daily short test and a long test once a month over weekends.
â mauzilla
Nov 29 '17 at 9:29
Thank you @Stephen, well answered! I've had some issues with smartd.conf not performing the tests so will setup a cronjob that first ensures offline test data is collected, run a manual daily short test and a long test once a month over weekends.
â mauzilla
Nov 29 '17 at 9:29
Thank you @Stephen, well answered! I've had some issues with smartd.conf not performing the tests so will setup a cronjob that first ensures offline test data is collected, run a manual daily short test and a long test once a month over weekends.
â mauzilla
Nov 29 '17 at 9:29
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f407681%2fsmartmontools-is-the-automatic-test-the-same-as-running-a-short-test%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password