From owner-freebsd-current Fri Jan 18 4:46:59 2002 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.99.75.166]) by hub.freebsd.org (Postfix) with ESMTP id 6DD0137B419; Fri, 18 Jan 2002 04:46:56 -0800 (PST) Received: (from uucp@localhost) by ns.plaut.de (8.9.3/8.9.3) with UUCP id NAA35800; Fri, 18 Jan 2002 13:45:39 +0100 (CET) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.11.3/8.8.8) with ESMTP id g0ICjJJ00612; Fri, 18 Jan 2002 13:45:19 +0100 (CET) (envelope-from root@nihil) Date: Fri, 18 Jan 2002 13:45:19 +0100 (CET) From: Michael Reifenberger To: Bruce Evans Cc: FreeBSD-Current , Subject: Re: panic during fdisk'ing a md(4) device In-Reply-To: <20020118232153.H792-100000@gamplex.bde.org> Message-ID: <20020118134228.D499-100000@nihil> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 18 Jan 2002, Bruce Evans wrote: ... > It somehow worked here, but after fixing the non-removal of the > /dev/md11*, I got back what is probably the original panic too. At > least with my fixed changes, the panic is caused by not clearing > pointers in destroy_dev(). The pointers come back in make_dev() and > bite you a little later. My orginal fixes helped by not doing all the > necessary calls to destroy_dev(). > > devfs still leaks 2 DEVFS allocations and 6 devbuf allocations for every > iteration of the script. ... Does this mean that your latest patch removes the panic but leaks some resources. Bye! ---- Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message