From owner-freebsd-current Thu Jul 19 9:58:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id B28F537B406 for ; Thu, 19 Jul 2001 09:58:41 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from wonky.feral.com (mjacob@wonky.feral.com [192.67.166.7]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f6JGwWS65150; Thu, 19 Jul 2001 09:58:33 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Thu, 19 Jul 2001 09:58:24 -0700 (PDT) From: Matthew Jacob Reply-To: To: Bruce Evans Cc: Subject: Re: fatal flaw in diskcheckd... In-Reply-To: Message-ID: <20010719095618.H50024-100000@wonky.feral.com> 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 Wed, 18 Jul 2001, Matthew Jacob wrote: > > > So, I took a SCSi disk away. Diskcheckd started complaining. However, > > a camcontrol rescan couldn't make the disk go away until I killed off > > diskcheckd, which then closed the disk, allowing the rescan to remove it. > > Bad. Bad. Bad. > > This may also have caused your disklabel problems. The old label doesn't > go away until all minors on the device are closed, at least when you clobber > the label using the dd hack. Ummm..... maybe... I think on that system I had disabled disckcheckd, but it's an excellent suggestion for me to check. With respect to diskcheckd, which in general is a neat tool to have around, I think it might be better if it did: open seek read close rather than leaving a disk open anyway. The difference between problems with an open as opposed to problems with a read are worth noting anyway. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message