I was reading about the -C (captive) option in the manpage which says:
WARNING: Tests run in captive mode may busy out the drive for the
length of the test. Only run captive tests on drives without any
What does it mean to "busy out the drive"? Does that mean make it very busy
rendering the system unusable for the duration of the test? Or, is it
actually performing write operations on the disk as part of the test which
could cause corruption on a mounted filesystem?
* Bruce Allen <ballen@...> [2006-05-24 13:54 -0500]:
> You can run tests 'in the foreground' with the -C (captive) option. Just
> don't do it with a mounted disk/file system!
> On Wed, 24 May 2006, Marc Tardif wrote:
> >I would like to perform smartctl tests from a script. The problem is
> >that the tests are run in the background. So, the script has to parse
> >the output of the command to determine how much time to wait. Then, the
> >script has to be conservative about the time to actually wait in case
> >smartctl takes a few seconds more than expected. Finally, the script
> >has to list the content of the device log.
> >Would it be possible to somehow run the tests in the foreground? This
> >would make it much simpler to write tests which could call smartctl and
> >wait on stdout.
> >Just in case, here is my version of smartmontools:
> >smartmontools release 5.32 dated 2004/07/05 at 08:10:26 UTC
> >smartmontools build host: i686-pc-linux-gnu
> >smartmontools build configured: 2005/07/18 13:49:57 UTC
> >smartctl compile dated Jul 18 2005 at 13:50:04
> >smartmontools configure arguments: '--prefix=/usr' '--sysconfdir=/etc'
> >'--mandir=/usr/share/man' '--with-initscriptdir=/etc/init.d'
> >'--with-docdir=/usr/share/doc/smartmontools' 'CFLAGS=-fsigned-char -Wall
> >Marc Tardif
> >All the advantages of Linux Managed Hosting--Without the Cost and Risk!
> >Fully trained technicians. The highest number of Red Hat certifications in
> >the hosting industry. Fanatical Support. Click to learn more
> >Smartmontools-support mailing list