Re: long tests automatically get interrupted
Andrew Engelbrecht <[email protected]>
| Newsgroups | gmane.linux.utilities.smartmontools |
|---|---|
| Message-ID | <[email protected]> |
On 06/13/2014 06:15 PM, Dan Lukes wrote: > On 06/14/14 00:06, Andrew Engelbrecht: >>> # 3 Extended captive Interrupted (host reset) 90% >>> 73 - > Do you have a specific reason to run test in captive mode ? i first tried captive mode as a work around after this early test: > # 5 Extended offline Interrupted (host reset) 40% 3 - after that failure, captive mode seemed like a potential solution but was counter-productive, since all those tests failed early on. i remembered the test in offline mode having failed for the same or similar reasons, but perhaps i was mistaken. would you like for me to make a section on the faq addressing this issue? the man page's section for --captive is almost clear enough: > WARNING: Tests run in captive mode may busy out the drive for > the length of the test. Only run captive tests on drives with‐ > out any mounted partitions! it would be clearer if that said: "... may busy out the drive for the length of the test. <This may cause the kernel to reset the device during an extended test. Also,> only run captive tests..." as it is, the first statement seems to be only relevant in support of the one that follows. thanks for your guidance. -andrew ------------------------------------------------------------------------------ HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems _______________________________________________ Smartmontools-support mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/smartmontools-support