From owner-freebsd-stable@FreeBSD.ORG Mon May 31 07:01:57 2010 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 8E1491065678 for ; Mon, 31 May 2010 07:01:57 +0000 (UTC) (envelope-from phil@amdg.etowns.org) Received: from nskntmtas05p.mx.bigpond.com (nskntmtas05p.mx.bigpond.com [61.9.168.149]) by mx1.freebsd.org (Postfix) with ESMTP id 222AA8FC18 for ; Mon, 31 May 2010 07:01:56 +0000 (UTC) Received: from nskntotgx03p.mx.bigpond.com ([58.172.114.57]) by nskntmtas05p.mx.bigpond.com with ESMTP id <20100531070155.IUDS18865.nskntmtas05p.mx.bigpond.com@nskntotgx03p.mx.bigpond.com> for ; Mon, 31 May 2010 07:01:55 +0000 Received: from mail.heuristicsystems.com.au ([58.172.114.57]) by nskntotgx03p.mx.bigpond.com with ESMTP id <20100531070154.GBSP1978.nskntotgx03p.mx.bigpond.com@mail.heuristicsystems.com.au> for ; Mon, 31 May 2010 07:01:54 +0000 Received: from white (white.hs [10.0.5.2]) (authenticated bits=0) by mail.heuristicsystems.com.au (8.14.3/8.13.6) with ESMTP id o4V71QZh046924 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Mon, 31 May 2010 17:01:26 +1000 (EST) (envelope-from phil@amdg.etowns.org) From: "Phil" To: Date: Mon, 31 May 2010 17:00:57 +1000 Organization: Heuristic Systems Pty Ltd Message-ID: <580CA5B8F8654FC782CC1137614582C3@HS> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Thread-Index: AcsAiKYatqCHIslkRy2GLFHBBFGBewAASoCQ X-RPD-ScanID: Class unknown; VirusThreatLevel unknown, RefID str=0001.0A090207.4C035EE2.00F0,ss=1,fgs=0 X-SIH-MSG-ID: rB43Ftz3TAD0zmQv0WC2O1J3yArnq3Mt8ZoaRdJjqwQZTULdvMbOPpX9Y94QiJ7l1S5MMRCFP2slZ7zmXY7RiA== Subject: 8.1 Pre-release gpart, isn't setting type correctly 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: Mon, 31 May 2010 07:01:57 -0000 Performing the following gpart commands on either a hard disk or usb memory stick doesn't correctly store the gpart type information. What we're doing, using FreeBSD 8.1-PRERELEASE, csuped as at 30-May-2010 23:59 UTC (*default date=2010.05.30.23.59.59) # gpart create -s GPT da1 # gpart add -s 1G -t freebsd-ufs da1 # gpart show da1 => 34 7827325 da1 GPT (3.7G) 34 2097152 1 !00000000-0000-0000-0000-000000000000 (1.0G) 2097186 5730173 - free - (2.7G) Expected to see something like: 34 2097152 1 freebsd-ufs (1.0G) # gpart list da1 Geom name: da1 fwheads: 255 fwsectors: 63 last: 7827358 first: 34 entries: 128 scheme: GPT Providers: 1. Name: da1p1 Mediasize: 1073741824 (1.0G) Sectorsize: 512 Mode: r0w0e0 rawtype: 00000000-0000-0000-0000-000000000000 label: (null) length: 1073741824 offset: 17408 type: !00000000-0000-0000-0000-000000000000 index: 1 end: 2097185 start: 34 Consumers: 1. Name: da1 Mediasize: 4007624704 (3.7G) Sectorsize: 512 Mode: r0w0e0 If I reboot the machine, only the /dev/da1 devices is recognised, there is no /dev/da1p1. Also "gpart modify -i 1 -t freebsd-ufs da1" did not have any effect on the "gpart list" We have a similar outcome when using the HDD, => 34 976773101 ada0 GPT (466G) 34 128 1 !00000000-0000-0000-0000-000000000000 (64K) 162 8388608 2 !00000000-0000-0000-0000-000000000000 (4.0G) 8388770 4194304 3 !00000000-0000-0000-0000-000000000000 (2.0G) 12583074 25165824 4 !00000000-0000-0000-0000-000000000000 (12G) 37748898 33554432 5 !00000000-0000-0000-0000-000000000000 (16G) 71303330 4096 6 !00000000-0000-0000-0000-000000000000 (2.0M) 71307426 10485760 7 !00000000-0000-0000-0000-000000000000 (5.0G) 81793186 33554432 8 !00000000-0000-0000-0000-000000000000 (16G) 115347618 566231040 9 !00000000-0000-0000-0000-000000000000 (270G) 681578658 16384 10 !00000000-0000-0000-0000-000000000000 (8.0M) 681595042 4194304 11 !00000000-0000-0000-0000-000000000000 (2.0G) 685789346 290983789 12 !00000000-0000-0000-0000-000000000000 (139G) Hardware: Used two different motherboards: Gigabyte (without ahci available) and VIA SN1800 (with ahci available and enabled); two hard disks (WD500AAKS)and one usb memory stick. Initially I thought it was the ahci timeouts, but using different motherboards, and a usb drive disproved that association. If there is anything that I can do, or provide to help resolve this, I'm happy to do so. Regards, Phil Sydney Australia (GMT+10 hours)