From owner-freebsd-hackers Fri Nov 7 10:00:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA13247 for hackers-outgoing; Fri, 7 Nov 1997 10:00:36 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA13242 for ; Fri, 7 Nov 1997 10:00:33 -0800 (PST) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id NAA20664; Fri, 7 Nov 1997 13:00:27 -0500 (EST) Date: Fri, 7 Nov 1997 13:00:27 -0500 (EST) From: Snob Art Genre To: Marc Slemko cc: hackers@FreeBSD.ORG Subject: Re: ufslk2 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Check out lsof -- I think it's in the ports collection. It can tell you what files are open and who is accessing them. On Thu, 6 Nov 1997, Marc Slemko wrote: > I have a news server that likes making innd hang in ufslk2 for periods of > up to 30 seconds every time a sync is done. > > Is there any easy way to find out what file system (or even file) it is > blocking on while the sync is happening? > > Most are mounted async. I have increased kern.update from the default of > 30 to something higher because it does give a performance gain. > Unfortunately, it results in longer periods of hang when it happens. > Decreasing it back to 30 results hurts the server overall, although it > does obviously reduce the time taken to sync each time (and therefore the > time innd hangs in ufslk2) a lot, but it still adds up to a similar > number. Yes, mounting async hurts this too but has a better overall > impact. > > Any work being done on having the system be nicer when syncing if it has a > large amount of data to sync? > > This is on 2.2-stable from a few months ago. > > > Ben "You have your mind on computers, it seems."