I am wondering how the SMART long selftest responds to
an increase in disk activity. For example, after kicking off a long selftest, I
start using the drive for continuous streaming
reads or streaming writes (using dd or sg_dd), how does
the SMART subsystem handle this?
Does the SMART subsystem temporarily pause
the selftest? Does the selftest resume after the activity ends (or is reduced),
or does one need to manually restart the test?
I couldn't find any detailed explanation on this.
Please let me know if this is documented someplace - I couldnt find it in
the man pages...