From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 10:05:53 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8130116A4CE for ; Thu, 22 Jul 2004 10:05:53 +0000 (GMT) Received: from dbmail-mx11.orcon.net.nz (loadbalancer1.orcon.net.nz [219.88.242.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id E64F043D2F for ; Thu, 22 Jul 2004 10:05:52 +0000 (GMT) (envelope-from pmurray@nevada.net.nz) Received: from [10.58.2.16] (port-222-152-49-103.fastadsl.net.nz [222.152.49.103])i6MA5Tkn026349; Thu, 22 Jul 2004 22:05:33 +1200 Message-ID: <40FF9173.1070403@nevada.net.nz> Date: Thu, 22 Jul 2004 22:05:39 +1200 From: Philip Murray User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <40FF8283.1030102@nevada.net.nz> <200407221139.03935@harryhomeworkstation> In-Reply-To: <200407221139.03935@harryhomeworkstation> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamd / ClamAV version 0.73, clamav-milter version 0.73a on dbmail-mx11.orcon.net.nz X-Virus-Status: Clean X-Spam-Status: -4.9, tests=BAYES_00 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on dbmail-mx11.orcon.net.nz cc: Harald Schmalzbauer Subject: Re: 3Ware 9500 and disklabel X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jul 2004 10:05:53 -0000 Harald Schmalzbauer wrote: >Am Donnerstag, 22. Juli 2004 11:01 schrieb Philip Murray: > > >>Hi, >> >>I'm trying to test out -CURRENT (22/7/2004) on a dual Opteron (Tyan >>board) with a 3Ware 9500-8 raid controller and I'm having problems with >>disklabel. >> >>At the moment I have a RAID0 array totalling 600GB. I fdisk'd them to >>create a single partition using the entire volume, fdisk (from >>sysinstall) complained about the geometry, I wasn't sure what the >>correct geometry was, so I forged ahead anyway. >> >>Then I went to try and disklabel it. It seemed to work from sysinstall >>until I went to write the changes out and it complained "ERROR: Unable >>to write data to disk da0!'. So I tried disklabel on the command line, as >>so >> >> > >AFAIK geom only prevents you from direct access to disks where your kernel >booted from. In your case it is ad4 and I think da1 shouldn't be affected but >perhaps you want to set the sysctl kern.geom.debugflags to 16. > > > Trying to use disklabel from sysinstall with those geom flags resulted in a panic, I got the following trace from the debugger: panic: spoiling cp->ace = 1 cpuid = 1; KDB: enter: panic [thread 100081] Stopped at kdb_enter+0x2f: nop db> trace kdb_enter() at kdb_enter+0x2f panic() at panic+0x210 g_spoil() at g_spoil+0x7a g_access() at g_access+0x1fb g_dev_open() at g_dev_open+0x11b spec_open() at spec_open+0x330 spec_vnoperate() at spec_vnoperate+0x14 vn_open_cred() at vn_open_cred+0x364 kern_open() at kern_open+0x109 syscall() at syscall+0x40e Xfast_syscall() at Xfast_syscall+0xa8 --- syscall (5, FreeBSD ELF64, open), rip = 0x50ebc0, rsp = 0x7fffffffd838, rbp = 0x7dd780 --- db> I don't know anything more useful I can do than that, so if there is something tell me. However, I have managed to somehow lockup the serial console so I can't do anymore until tomorrow. Cheers Philip