From owner-freebsd-stable@FreeBSD.ORG Fri Dec 9 15:57:44 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3860C16A41F for ; Fri, 9 Dec 2005 15:57:44 +0000 (GMT) (envelope-from jason.harmening@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2CF6243D5C for ; Fri, 9 Dec 2005 15:57:43 +0000 (GMT) (envelope-from jason.harmening@gmail.com) Received: by zproxy.gmail.com with SMTP id i11so874016nzh for ; Fri, 09 Dec 2005 07:57:42 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=Jb8aUk3lL7CTmED0xIs8vC5DCWrKla7BKF6+X140zEVz9ACKySGhAPDdgjXFDu5AWBifby40LopROhsa3bXUsr9HDVloT0uxlDeyDXSw/xk5IHL2FCcO9HQ9k1soRBXhLgIoeuVBeUcADbjNumZdydGOKIVU2JvdA6aIimUfzw0= Received: by 10.36.251.49 with SMTP id y49mr3576849nzh; Fri, 09 Dec 2005 07:57:42 -0800 (PST) Received: by 10.36.154.19 with HTTP; Fri, 9 Dec 2005 07:57:42 -0800 (PST) Message-ID: <2d1264630512090757n65c60cf0rb64385f3fac7321b@mail.gmail.com> Date: Fri, 9 Dec 2005 09:57:42 -0600 From: Jason Harmening To: gbyshenk@byshenk.net In-Reply-To: <200512090015.jB90FMEA084040@byshenk.demon.nl> MIME-Version: 1.0 References: <200512090015.jB90FMEA084040@byshenk.demon.nl> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: [FreeBSD 6.0-RELEASE] Incorrect geometry for VIA RAID0 array X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 15:57:44 -0000 Yes, the array is being recognized properly. The problem seems to be in th= e via_read_meta() function in sys/dev/ata/ata_raid.c. Essentially, the problem is that in the case of a striped array, the function overwrites the total sector count of the top-level raid descriptor with the sector count o= f each enumerated disk, rather than adding to the sector count. Last night I installed FreeBSD on the first half of the array, and then built a custom kernel with a modification to fix this issue. The full 148G capacity of th= e array is now recognized, and I've been able to expand my slice with fdisk and bsdlabel/newfs a new partition in the added space. So far I've written about a gig of data to the new partition, and everything is working fine. Note that even if you had a striped array, you wouldn't see this issue because in your case the OS would use the promise_read_meta() routine, whic= h doesn't have this bug. On 12/8/05, greg byshenk wrote: > > On freebsd-stable, jason.harmening@gmail.com (Jason Harmening) wrote: > > > Here's the dmesg output from the installer: > > > ad4: 70911MB at ata2-master SATA150 > > ad6: 70911MB at ata3-master SATA150 > > ar0: 70911MB status: READY > > ar0: disk0 READY using ad4 at ata2-master > > ar0: disk1 READY using ad6 at ata3-master > > Are you _sure_ that the array is being recognized properly? > > Based on the dmesg output, it looks like the controller is being read > as a 74G drive. > > FWIW, this is the section of my dmesg output, for a _mirror_: > > ad4: 78167MB at ata2-master UDMA133 > ad6: 78167MB at ata3-master UDMA133 > ar0: 77247MB status: READY > ar0: disk0 READY (master) using ad4 at ata2-master > ar0: disk1 READY (mirror) using ad6 at ata3-master > > > > On 12/7/05, Jason Harmening wrote: > > > > I'm trying to install FreeBSD 6.0-RELEASE on a RAID0 array attached t= o > the > > > VIA 8237 controller on my Asus A8V Deluxe motherboard. The array > consists > > > of two 74G drives. The installer recognizes the array as ar0, but > when I > > > enter FDISK to set up my partition, the size of the array is only > recognized > > > as 74G, rather than the true 148G. I've double-checked all my BIOS > > > settings, and nothing seems out of order. Please help! > > > -- > greg byshenk - gbyshenk@byshenk.net - Leiden, NL >