From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: RAID-10 keeps aborting Date: Tue, 11 Jun 2013 21:07:59 -0700 Message-ID: <51B7F41F.9000605@zytor.com> References: <51AC1440.7020505@zytor.com> <51AC3283.4000403@zytor.com> <51ACBAA0.40604@zytor.com> <51ACD511.4030604@zytor.com> <51AE2A8C.4080508@zytor.com> <51AE3441.3000208@zytor.com> <51AEA4FE.3060900@zytor.com> <20130606142747.1fc17b7f@ jlaw-desktop.mno.stratus.com> <20130610101505.33b32d07@jlaw-desktop.mno.stratus.com> <20130612131543.1c79e077@notabene.brown> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20130612131543.1c79e077@notabene.brown> Sender: linux-raid-owner@vger.kernel.org To: NeilBrown Cc: Joe Lawrence , "Martin K. Petersen" , Dan Williams , linux-raid List-Id: linux-raid.ids On 06/11/2013 08:15 PM, NeilBrown wrote: > If a drive reports that WRITE SAME works, but it doesn't, then I'm > not sure that I can be happy about working with that drive. Seriously... we have that kind of problems all over the place with all kinds of hardware. Falling back is sensible... the problem here is *where* that needs to happen... the block layer already does, apparently. > If a drive has some quirky behaviour wrt WRITE SAME, then that > should be handled in some place where 'quirks' are handled - > certainly not in md. The problem here is that you don't find out ahead of time. Now, if I understand the issue at hand correctly is that the reporting here was actually a Linux bug related to SATA drives behind a SAS controller. Martin, am I right? -hpa