On Fri, Jun 3, 2016 at 8:11 AM, Martin <rc6encryp...@gmail.com> wrote: >> Make certain the kernel command timer value is greater than the driver >> error recovery timeout. The former is found in sysfs, per block >> device, the latter can be get and set with smartctl. Wrong >> configuration is common (it's actually the default) when using >> consumer drives, and inevitably leads to problems, even the loss of >> the entire array. It really is a terrible default. > > Are nearline SAS drives considered consumer drives?
No, they should have configurable sct erc setting using smartctl. Many, possibly most, consumer drives now do not support it, so often the only workable way to use them in any kind of multiple device scenario other than linear/concat or raid0 is to significantly increase the scsi command timer - upwards or 2 or 3 minutes. So if your use case cannot tolerate such delays, then the drives must be disqualified. -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
