From owner-freebsd-stable Sun Feb 10 11:11:58 2002 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 95E8B37B402 for ; Sun, 10 Feb 2002 11:11:56 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1AJBOk30917; Sun, 10 Feb 2002 11:11:24 -0800 (PST) (envelope-from dillon) Date: Sun, 10 Feb 2002 11:11:24 -0800 (PST) From: Matthew Dillon Message-Id: <200202101911.g1AJBOk30917@apollo.backplane.com> To: Mike Silbersack Cc: Valentin Nechayev , "David W. Chapman Jr." , Subject: Re: cvs commit: src/sys/ufs/ffs ffs_softdep.c References: <20020210113348.P28078-100000@patrocles.silby.com> 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 :... :> 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 Hmm. I will attempt to reproduce the problem. How much activity is 'significant' ? e.g. equivalent of an rm -rf /usr/ports or something smaller? Do the directories have to be deeply nested for the problem to occur? On the second issue - long disk activity times after a 'syncing disks... done'. This can occur if there are a lot of dirty VM pages in the system belonging to files that need to be written out. This can take an especially long time if a large file was created with ftruncate() and written via mmap() instead of write(), because the file can become severely fragmented. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message