From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-io0-f194.google.com ([209.85.223.194]:35200 "EHLO mail-io0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932377AbcFCPd6 (ORCPT ); Fri, 3 Jun 2016 11:33:58 -0400 Received: by mail-io0-f194.google.com with SMTP id k19so10681713ioi.2 for ; Fri, 03 Jun 2016 08:33:57 -0700 (PDT) Subject: Re: Recommended why to use btrfs for production? To: Martin , Chris Murphy References: Cc: Btrfs BTRFS From: "Austin S. Hemmelgarn" Message-ID: <156f60b2-d666-d553-194b-c09de041d476@gmail.com> Date: Fri, 3 Jun 2016 11:33:54 -0400 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Sender: linux-btrfs-owner@vger.kernel.org List-ID: On 2016-06-03 10:11, Martin 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? > If it's a SAS drive, then no, especially when you start talking about things marketed as 'nearline'. Additionally, SCT ERC is entirely a SATA thing, I forget what the equivalent in SCSI (and by extension SAS) terms is, but I'm pretty sure that the kernel handles things differently there.