From owner-freebsd-bugs@FreeBSD.ORG Mon Jun 23 15:50:17 2003 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A74C337B401 for ; Mon, 23 Jun 2003 15:50:17 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4827643F93 for ; Mon, 23 Jun 2003 15:50:17 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h5NMoGUp054081 for ; Mon, 23 Jun 2003 15:50:16 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h5NMoG8O054080; Mon, 23 Jun 2003 15:50:16 -0700 (PDT) Date: Mon, 23 Jun 2003 15:50:16 -0700 (PDT) Message-Id: <200306232250.h5NMoG8O054080@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: "Pawel Malachowski" Subject: Re: kern/52916: vinum causes panic after start/stop/... cycle, easy to reproduce X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Pawel Malachowski List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2003 22:50:18 -0000 The following reply was made to PR kern/52916; it has been noted by GNATS. From: "Pawel Malachowski" To: Greg 'groggy' Lehey Cc: Freebsd-gnats-submit@FreeBSD.org Subject: Re: kern/52916: vinum causes panic after start/stop/... cycle, easy to reproduce Date: Tue, 24 Jun 2003 00:43:54 +0200 On 24 Jun 2003 at 7:52, Greg 'groggy' Lehey wrote: > I'd appreciate answers to my questions. Also a backtrace would help. This was from 9 Jun 2003: dscheck(cf703f08,c31a5f00) at dscheck+0x104 diskstrategy(cf703f08,c2f79d80,1,e194ae3c) at diskstrategy+0x7d spec_strategy(e194ae20,cf703f08,1,0,c041a6e0) at spec_strategy+0x8c ufs_strategy(e194ae64,e194ae70,c0240606,e194ae64,cf703f08) at ufs_strategy+0xc5 ufs_vnoperate(e194ae64) at ufs_vnoperate+0x15 bwrite(cf703f08,e194ae88,c024e4d,e194aea0,e194ae94) at bwrite+0x20a vop_stdwrite(e194aea0,e194ae94,c032ff61,e194aea0,e194aeac) at vop_stdwrite+0xe vop_defaultop(e194aea0,e194aeac,c0240956,e194aea0,c041a920) at vop_defaultop+0x15 ufs_vnoperate(e194aea0,c041a920,e1953300,cf703f08,e194aee8) at ufs_vnoperate+0x15 bawrite(cf703f08,0,cf703f08,e1953300,0) at bawrite+0x32 ffs_fsync(e194af08,da0baf60,1,e194af80,c04887c0) at ffs_fsync+0x1e2 fsync(da0baf60,e194af80,8053800,bfbfede8,8054cd5) at fsync+0xa8 syscall2(2f2f2f,8054cd5,bfbfede8) at syscall2+0x1f5 Xint0x80_syscall() at Xint0x80_syscall+0x25 Will provide fresh one tommorow. What would You like to know? I'll try to answer. -- Paweł Małachowski