From owner-freebsd-fs@FreeBSD.ORG  Fri Mar  2 21:36:33 2012
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 72267106576A;
	Fri,  2 Mar 2012 21:36:33 +0000 (UTC)
	(envelope-from mckusick@mckusick.com)
Received: from chez.mckusick.com (unknown
	[IPv6:2001:5a8:4:7e72:4a5b:39ff:fe12:452])
	by mx1.freebsd.org (Postfix) with ESMTP id 507F68FC17;
	Fri,  2 Mar 2012 21:36:33 +0000 (UTC)
Received: from chez.mckusick.com (localhost [127.0.0.1])
	by chez.mckusick.com (8.14.3/8.14.3) with ESMTP id q22LaTvj037524;
	Fri, 2 Mar 2012 13:36:29 -0800 (PST)
	(envelope-from mckusick@chez.mckusick.com)
Message-Id: <201203022136.q22LaTvj037524@chez.mckusick.com>
To: Ivan Voras <ivoras@freebsd.org>
In-reply-to: <CAF-QHFUBEsZ-KJ86Btr+wcvynraTAGz9BJ3e0Wyw95tdyMzogA@mail.gmail.com>
Date: Fri, 02 Mar 2012 13:36:29 -0800
From: Kirk McKusick <mckusick@mckusick.com>
X-Spam-Status: No, score=0.0 required=5.0 tests=MISSING_MID, UNPARSEABLE_RELAY
	autolearn=failed version=3.2.5
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on chez.mckusick.com
Cc: freebsd-fs@freebsd.org
Subject: Re: fsync: giving up on dirty 
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2012 21:36:33 -0000

> From: Ivan Voras <ivoras@freebsd.org>
> Date: Fri, 2 Mar 2012 12:57:00 +0100
> Subject: Re: fsync: giving up on dirty
> To: Kirk McKusick <mckusick@mckusick.com>
> Cc: freebsd-fs@freebsd.org
> 
> On 29 February 2012 20:19, Kirk McKusick <mckusick@mckusick.com> wrote:
> 
> > I believe that the problem is because the soft updates worklist needs
> > to be flushed before some of the dirty blocks can be successfully written.
> > If you are running a 9-stable system on this machine, are using journaled
> > soft updates on the filesystem in question, and are willing to try out
> > my first attempt at a fix, let me know and I'll send you the diffs for it.
> 
> The thing is - I'm not. This is a 9-stable, but it was upgraded from 8
> and I don't have SUJ enabled.
> 
> I keep getting such messages daily.
> 
> Mar  1 04:02:09 skynet kernel: fsync: giving up on dirty
> Mar  1 04:02:09 skynet kernel: 0xfffffe000fef2780: tag devfs, type VCHR
> Mar  1 04:02:09 skynet kernel: usecount 1, writecount 0, refcount 2515
> mountedhere 0xfffffe000fd25200
> Mar  1 04:02:09 skynet kernel: flags ()
> Mar  1 04:02:09 skynet kernel: v_object 0xfffffe000fe96d98 ref 0 pages 10182
> Mar  1 04:02:09 skynet kernel: lock type devfs: EXCL by thread
> 0xfffffe003dc8d000 (pid 79344)
> Mar  1 04:02:09 skynet kernel: dev multipath/hpdisk4-web

Thanks for the report. It is useful to know that this can occur even
with non SUJ systems. I am working with Peter Holm to identify the
cause and will keep you (and the list) posted with what we figure out.

	Kirk McKusick