From owner-freebsd-hardware@FreeBSD.ORG Tue Jan 15 20:38:43 2013 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 5FF8DFC9; Tue, 15 Jan 2013 20:38:43 +0000 (UTC) (envelope-from landsidel.allen@gmail.com) Received: from mail-vc0-f178.google.com (mail-vc0-f178.google.com [209.85.220.178]) by mx1.freebsd.org (Postfix) with ESMTP id 0FA93721; Tue, 15 Jan 2013 20:38:42 +0000 (UTC) Received: by mail-vc0-f178.google.com with SMTP id l6so584194vcl.23 for ; Tue, 15 Jan 2013 12:38:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=LGXylZR/pV7eo9guB/oQE8yXdD0Fq4sJJipw4jDHkVI=; b=r53HQwvgjYXbAKYzRoJ9ZAluYj/CQoeZqAmkFiyE2tmB9+vWDSbkkY/3N6OBBi0bRV Y2sG+MZwJ/76NaMqzxHBebltylggWUi2CEY5yayeqzekslNgEwX/O7Q80O6RX6vtdsur Xm0wCaBzhuttUKKsDnbD10fHNXbbjeVv1pUcZn5kSwy3G6gU5ja6zHtpIjil2J1CWTmE LoFP+tPtZ2QJiwVZ3Z2keJr8dbf9P28f4rRnmK8i0+95kr6JpZDGfeT1PKODNJS/8QJI AelatbeWjMpVvW3pVGcQHnkdU+w8gIcGukzlZKet0dU/2h9krcT4NjLsYGdk5lEWlz6Y RcuQ== X-Received: by 10.52.21.13 with SMTP id r13mr26235537vde.37.1358282318495; Tue, 15 Jan 2013 12:38:38 -0800 (PST) Received: from [192.168.130.0] (c-66-30-48-132.hsd1.nh.comcast.net. [66.30.48.132]) by mx.google.com with ESMTPS id t6sm9169850vdf.18.2013.01.15.12.38.36 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 15 Jan 2013 12:38:37 -0800 (PST) Message-ID: <50F5BE48.2090508@gmail.com> Date: Tue, 15 Jan 2013 15:38:32 -0500 From: Allen Landsidel User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: John Baldwin Subject: Re: Fwd: Re: bin/166589: atacontrol(8) incorrectly treats RAID10 and 0+1 the same References: <50F57C0D.1010608@FreeBSD.org> <50F57EB5.1060801@gmail.com> <201301151413.22505.jhb@freebsd.org> In-Reply-To: <201301151413.22505.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hardware@freebsd.org X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jan 2013 20:38:43 -0000 Several updates have occurred since the email, I think I've explained it to him well enough. Yes, there is a difference. A "fakeraid" / firmware RAID0+1 with two failed disks will not boot. A RAID10 will, if it's not the "wrong" 2nd disk. Even though the OS has no control over this behavior, it's not doing anyone any favors to suppressed or obscure the what the hardware is capable of. A RAID0+1 is a no-buy for many, including myself. A controller sold claiming to do RAID10 that actually does 0+1 is an RMA item. On 1/15/2013 14:13, John Baldwin wrote: > On Tuesday, January 15, 2013 11:07:17 am Allen Landsidel wrote: >> http://www.freebsd.org/cgi/query-pr.cgi?pr=166589&cat= >> >> Can somebody else talk some sense into this guy? I'm losing my temper. > Well, is his last question correct? If the RAID BIOS writes the metadata > the same way regardless, then is there a reason (beyond "pure correctness") to > not just treat RAID0+1 as RAID10? > >> -------- Original Message -------- >> Subject: Re: bin/166589: atacontrol(8) incorrectly treats RAID10 and >> 0+1 the same >> Date: Tue, 15 Jan 2013 17:55:57 +0200 >> From: Alexander Motin >> To: Allen Landsidel >> CC: bug-followup@FreeBSD.org >> >> >> >> Their on-disk formats are identical. Even if RAID BIOS supports RAID0+1, >> there is no problem to handle it as RAID10 at the OS level. That gives >> better reliability without any downsides. I think there is much higher >> chance that inexperienced user will choose RAID0+1 by mistake, then >> experienced wish do to it on intentionally. Do you know any reason why >> RAID0+1 can't be handled as RAID10? >> >> On 15.01.2013 17:28, Allen Landsidel wrote: >>> Most devices typically only support one level or the other, but not >>> both. I don't "Insist that it should exist", it *does* exist. Both >>> levels do, and they are not the same thing. >>> >>> As for why it should be "available" to the user, I think that's a pretty >>> silly question. If their hardware supports one or both levels, they >>> should be available to the user -- and called by their correct names. >>> >>> On 1/15/2013 03:12, Alexander Motin wrote: >>>> That is clear and I had guess you mean it, but why do you insist that >>>> such RAID0+1 variant should even exist if it has no benefits over >>>> RAID10, and why it should be explicitly available to user? >>>> >>>> On 15.01.2013 04:51, Allen Landsidel wrote: >>>>> They are not variants in terminology, they are different raid levels. >>>>> Raid0+1 is two RAID-0 arrays, mirrored into a RAID-1. if one of the >>>>> disks fails, that entire RAID-0 is offline and must be rebuilt, and all >>>>> redundancy is lost. A RAID-10 is composed of N raid-1 disks combined >>>>> into a RAID-0. If one disk fails, only that particular RAID-1 is >>>>> degraded, and the redundancy of the others is maintained. >>>>> >>>>> 0+1 cannot survive two failed disks no matter how many are in the >>>>> array. 10 can survive half the disks failing, if it's the right half. >>>>> >>>>> This is something people who've never used more than 4 disks fail to >>>>> grasp, but those of us with 6 (or many many more) know very well. >>>>> >>>>> On 1/14/2013 21:46, Alexander Motin wrote: >>>>>> There could be variants in terminology, but in fact for most of users >>>>>> they are the same. If you have opinion why they should be treated >>>>>> differently, please explain it. >> >> -- >> Alexander Motin >> >> >> >> _______________________________________________ >> freebsd-hardware@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hardware >> To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" >>