From owner-freebsd-stable Sun Feb 10 9:32:53 2002 Delivered-To: freebsd-stable@freebsd.org Received: from patrocles.silby.com (d31.as13.nwbl0.wi.voyager.net [169.207.135.159]) by hub.freebsd.org (Postfix) with ESMTP id A910537B402 for ; Sun, 10 Feb 2002 09:32:48 -0800 (PST) Received: from localhost (silby@localhost) by patrocles.silby.com (8.11.6/8.11.6) with ESMTP id g1ABaKJ28116; Sun, 10 Feb 2002 11:36:20 GMT (envelope-from silby@silby.com) X-Authentication-Warning: patrocles.silby.com: silby owned process doing -bs Date: Sun, 10 Feb 2002 11:36:20 +0000 (GMT) From: Mike Silbersack To: Valentin Nechayev Cc: Matthew Dillon , "David W. Chapman Jr." , Subject: Re: cvs commit: src/sys/ufs/ffs ffs_softdep.c In-Reply-To: <20020210140547.A8068@iv.nn.kiev.ua> Message-ID: <20020210113348.P28078-100000@patrocles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 10 Feb 2002, Valentin Nechayev wrote: > 4.5-release contains 1.57.2.9, and I saw such problems 3 times. > Mostly this was after my games with ultradeep directories (up to 1000 nesting > directories), but all games used only correct syscall entries and their calls. > There was 2 occurences of another variant: __after__ message "Syncing disks... > N M\nDone\n", disk activity raised and on 2nd occurence stopped after > ~10 seconds, on 1st occurence I wait more than 1 minute for it to terminate > and at the end pressed Reset. Yes, I noticed this problem again as well. As you say, it only happens if there has been significant activity right before the shutdown. I didn't grab a crashdump as I was more worried about what I was testing at the time. Matt, can you reproduce the problem over by you? It seems that doing anything disk intensive and then shutting down immediately will trigger it. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message