From owner-freebsd-stable@FreeBSD.ORG Fri Sep 11 10:21:49 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D4C1D1065670 for ; Fri, 11 Sep 2009 10:21:49 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 652CC8FC12 for ; Fri, 11 Sep 2009 10:21:48 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.50) id 1Mm3GF-0004Dy-O9 for freebsd-stable@freebsd.org; Fri, 11 Sep 2009 12:21:47 +0200 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 11 Sep 2009 12:21:47 +0200 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 11 Sep 2009 12:21:47 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Fri, 11 Sep 2009 12:21:39 +0200 Lines: 77 Message-ID: References: <4AAA1296.2080705@sasktel.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 2.0.0.22 (X11/20090817) In-Reply-To: <4AAA1296.2080705@sasktel.net> Sender: news Subject: Re: 8.0-B4 gstripe / GEOM_PART_* upgrade woes 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, 11 Sep 2009 10:21:49 -0000 Stephen Hurd wrote: > I've upgraded from 7.2-RELEASE_p2 to 8.0-BETA4 and using GEOM_PART_* > with my sliced gstripe array causes the /dev/stripe/raid0a to disappear > and the reset of the /dev/stripe/raid0[a-z] file systems to be unmountable. > > My gvinum array is still working fine and, after chasing the ad* slices, > they can be mounted as well. It's just the gstripe slices which are > corrupt/missing. Ouch. > GEOM_STRIPE: Device raid0 created (id=40432321). > GEOM_STRIPE: Disk da0s2 attached to raid0. > GEOM_STRIPE: Disk da1s2 attached to raid0. > GEOM_STRIPE: Disk da2s2 attached to raid0. > GEOM_STRIPE: Disk da3s2 attached to raid0. > GEOM_STRIPE: Device raid0 activated. > Trying to mount root from ufs:/dev/da0s1a > <<111188>C>aCna'tn 'stta ts t/atd e/vd/aedv0s/1sgt:ri pNeo/ rsuacidh0 > af:i lNeo sour directory > c > =========== END OF dmesg =========== > > =========== gstripe list =========== > Geom name: raid0 > State: UP > Status: Total=4, Online=4 > Type: AUTOMATIC > Stripesize: 262144 > ID: 40432321 > Providers: > 1. Name: stripe/raid0 > Mediasize: 42934992896 (40G) > Sectorsize: 512 > Mode: r0w0e0 > Consumers: > 1. Name: da0s2 > Mediasize: 10733990400 (10G) > Sectorsize: 512 > Mode: r0w0e0 > Number: 0 > 2. Name: da1s2 > Mediasize: 10733990400 (10G) > Sectorsize: 512 > Mode: r0w0e0 > Number: 1 > 3. Name: da2s2 > Mediasize: 10733990400 (10G) > Sectorsize: 512 > Mode: r0w0e0 > Number: 2 > 4. Name: da3s2 > Mediasize: 10733990400 (10G) > Sectorsize: 512 > Mode: r0w0e0 > Number: 3 > =========== END OF gstripe list =========== > > =========== gstripe status =========== > Name Status Components > stripe/raid0 UP da0s2 > da1s2 > da2s2 > da3s2 > =========== END OF gstripe status =========== > When I build without GEOM_PART_* and use GEOM_BSD and GEOM_MBR, it works > fine. An interesting problem. I presume that in either case (gpart or GEOM_BSD/MBR) the output of "gstripe status" is the same? Only the interpretation of the partition tables is problematic? What is the expected ("good") structure of the partitions/file systems? Do you have a single MBR partition and inside it multiple BSD partitions? What are their partition types?