From owner-freebsd-fs@FreeBSD.ORG Fri Mar 2 13:03:52 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 05763106564A for ; Fri, 2 Mar 2012 13:03:52 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) by mx1.freebsd.org (Postfix) with ESMTP id B2C998FC08 for ; Fri, 2 Mar 2012 13:03:51 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1S3S9H-0002Fc-0S for freebsd-fs@freebsd.org; Fri, 02 Mar 2012 14:03:51 +0100 Received: from dyn1218-51.wlan.ic.ac.uk ([129.31.218.51]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 02 Mar 2012 14:03:51 +0100 Received: from johannes by dyn1218-51.wlan.ic.ac.uk with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 02 Mar 2012 14:03:51 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Johannes Totz Date: Fri, 02 Mar 2012 13:03:37 +0000 Lines: 42 Message-ID: References: <201202291919.q1TJJfCP082878@chez.mckusick.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: dyn1218-51.wlan.ic.ac.uk User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 In-Reply-To: Subject: Re: fsync: giving up on dirty X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Mar 2012 13:03:52 -0000 On 02/03/2012 11:57, Ivan Voras wrote: > On 29 February 2012 20:19, Kirk McKusick wrote: >>> To: freebsd-fs@freebsd.org >>> From: Ivan Voras >>> Date: Wed, 29 Feb 2012 12:08:51 +0100 >>> Subject: fsync: giving up on dirty >>> >>> Hi, >>> >>> One of the machines I take care of started recently started recording >>> messages such as these in the logs: >>> >>> Feb 28 04:02:09 skynet kernel: fsync: giving up on dirty > ... >> 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 A while back I got similar messages (should be in the archives somewhere). Eventually it led to filesystem corruption with a kernel panic. It seemed to be related to snapsot creation (soft-updates, no journal). fsck and manually deleting all snapshots solved the problem temporarily. But when I stopped doing UFS snapshots alltogether the messages stopped too...