From owner-freebsd-current@FreeBSD.ORG Thu Oct 19 21:06:26 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 C268316A40F for ; Thu, 19 Oct 2006 21:06:26 +0000 (UTC) (envelope-from mjacob@freebsd.org) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5785243D66 for ; Thu, 19 Oct 2006 21:06:26 +0000 (GMT) (envelope-from mjacob@freebsd.org) Received: from ns1.feral.com (localhost [127.0.0.1]) by ns1.feral.com (8.13.8/8.13.8) with ESMTP id k9JL6QFV080521 for ; Thu, 19 Oct 2006 14:06:26 -0700 (PDT) (envelope-from mjacob@freebsd.org) Received: from localhost (mjacob@localhost) by ns1.feral.com (8.13.8/8.13.8/Submit) with ESMTP id k9JL6Q02080518 for ; Thu, 19 Oct 2006 14:06:26 -0700 (PDT) (envelope-from mjacob@freebsd.org) X-Authentication-Warning: ns1.feral.com: mjacob owned process doing -bs Date: Thu, 19 Oct 2006 14:06:26 -0700 (PDT) From: mjacob@freebsd.org X-X-Sender: mjacob@ns1.feral.com To: freebsd-current@freebsd.org Message-ID: <20061019140524.R80128@ns1.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: more geom panics X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mjacob@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Oct 2006 21:06:26 -0000 -current as of a couple days ago... Anyone have a clue as to why this might have happened? ...I had a virtual san device up and down a lot... (like a *lot*). The device had truly gone away, as in: (da0:isp0:0:6:0): Invalidating pack ... (da0:isp0:0:6:0): removing device entry .... After putting it back up, I had this: ... da0 at isp0 bus 0 target 6 lun 0 da0: Fixed Direct Access SCSI-4 device da0: 200.000MB/s transfers, Tagged Queueing Enabled da0: 1024MB (2097152 512 byte sectors: 64H 32S/T 1024C) ... So, I check the label: zorko.in1.lcl > sudo disklabel da0 # /dev/da0: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 2097136 16 4.2BSD 2048 16384 28528 c: 2097152 0 unused 0 0 # "raw" part, ... And try to run a test: zorko.in1.lcl > sudo patchk /dev/da0a 512 c /dev/da0a: Device not configured Huh? Relabel it: zorko.in1.lcl > sudo -Brw da0 auto Try again: zorko.in1.lcl > sudo patchk /dev/da0a 512 c /dev/da0a: Device not configured Decide to wipe the front: zorko.in1.lcl > sudo lmdd of=/dev/da0 ^C28.95 MB in 1.13 seconds (25.5841 MB/sec) Try to put a new label on it again: zorko.in1.lcl > sudo disklabel -Brw da0 auto And...BLAM: Fatal trap 9: general protection fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x8:0xffffffff80639f36 stack pointer = 0x10:0xffffffffac232b00 frame pointer = 0x10:0xffffffffac232b50 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 2 (g_event) [thread pid 2 tid 100007 ] Stopped at bcopy+0x16: repe movsq (%rsi),%es:(%rdi) db> bt Tracing pid 2 tid 100007 td 0xffffff021ef082b0 bcopy() at bcopy+0x16 gctl_set_param_err() at gctl_set_param_err+0x1c g_bsd_config() at g_bsd_config+0x97 g_ctl_req() at g_ctl_req+0x83 g_run_events() at g_run_events+0x203 g_event_procbody() at g_event_procbody+0x77 fork_exit() at fork_exit+0xaa fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffffffac232d40, rbp = 0 --- db> Sigh. -matt