From owner-freebsd-bugs@FreeBSD.ORG Mon Jun 23 15:30:14 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 5D16837B401 for ; Mon, 23 Jun 2003 15:30:14 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0BBB43F75 for ; Mon, 23 Jun 2003 15:30:13 -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 h5NMUDUp053448 for ; Mon, 23 Jun 2003 15:30:13 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h5NMUDH2053447; Mon, 23 Jun 2003 15:30:13 -0700 (PDT) Date: Mon, 23 Jun 2003 15:30:13 -0700 (PDT) Message-Id: <200306232230.h5NMUDH2053447@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: "Greg 'groggy' Lehey" 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: Greg 'groggy' Lehey List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2003 22:30:14 -0000 The following reply was made to PR kern/52916; it has been noted by GNATS. From: Greg 'groggy' Lehey To: Pawel Malachowski 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 07:52:35 +0930 --fRqxu2t+6O910vVH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Monday, 23 June 2003 at 23:40:36 +0200, Pawel Malachowski wrote: > On 6 Jun 2003 at 14:52, Greg 'groggy' Lehey wrote: > >> I'm guessing this has something to do with md devices. Do you use >> any? I don't, and every 'vinum start' created one. I've committed a >> fix to vinum(8) (revision 1.31.2.6 of src/sbin/vinum/commands.c). >> Please try it and tell me if it fixes the problem. > > Problem appears when we call (f)sync() while `vinum start' command is working. > After killing syslogd (which was using fsync(), I have both /var/log and /dev > on / fs with SoftUpdates enabled), stability increased. > > I was running /bin/sync frequently during vinum start/stop loop and sometimes I > can see `rm' (and other commands called from make_devices(), src/sbin/vinum/v.c) > complaining it was not possible to remove/recreate device files in /dev/vinum. > Panic happened within few seconds. I'd appreciate answers to my questions. Also a backtrace would help. Greg -- See complete headers for address and phone numbers --fRqxu2t+6O910vVH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE+932rIubykFB6QiMRAvJGAJ4jWOMeTnptkF2MSO0Zx3mtOdZWEgCfXJPI oVQLrEW0qedWFi22JXRhd4g= =RXj2 -----END PGP SIGNATURE----- --fRqxu2t+6O910vVH--