From owner-freebsd-fs@FreeBSD.ORG Thu Aug 29 15:10:05 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 1B47E1B1 for ; Thu, 29 Aug 2013 15:10:05 +0000 (UTC) (envelope-from longwitz@incore.de) Received: from dss.incore.de (dss.incore.de [195.145.1.138]) by mx1.freebsd.org (Postfix) with ESMTP id CFC5A2EE0 for ; Thu, 29 Aug 2013 15:10:04 +0000 (UTC) Received: from inetmail.dmz (inetmail.dmz [10.3.0.3]) by dss.incore.de (Postfix) with ESMTP id 6EC1E5D558 for ; Thu, 29 Aug 2013 17:03:45 +0200 (CEST) X-Virus-Scanned: amavisd-new at incore.de Received: from dss.incore.de ([10.3.0.3]) by inetmail.dmz (inetmail.dmz [10.3.0.3]) (amavisd-new, port 10024) with LMTP id hs7J9kXEe-Lp for ; Thu, 29 Aug 2013 17:03:44 +0200 (CEST) Received: from mail.incore (fwintern.dmz [10.0.0.253]) by dss.incore.de (Postfix) with ESMTP id 8843C5D561 for ; Thu, 29 Aug 2013 17:03:44 +0200 (CEST) Received: from bsdlo.incore (bsdlo.incore [192.168.0.84]) by mail.incore (Postfix) with ESMTP id 81E9B50962 for ; Thu, 29 Aug 2013 17:03:44 +0200 (CEST) Message-ID: <521F62D0.8000400@incore.de> Date: Thu, 29 Aug 2013 17:03:44 +0200 From: Andreas Longwitz User-Agent: Thunderbird 2.0.0.19 (X11/20090113) MIME-Version: 1.0 To: freebsd-fs@freebsd.org Subject: fsync: giving up on dirty on partitions with gjournal or soft updates Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Aug 2013 15:10:05 -0000 Hello, I run Freebsd 8.4-Stable r253040 completed with adapted r244795, r244925 and r245286 from head. On my servers with gjournaled partitions I sometimes see messages like this: serv02 kernel: fsync: giving up on dirty serv02 kernel: 0xffffff0002d313b0: tag devfs, type VCHR serv02 kernel: usecount 1, writecount 0, refcount 35 i mountedhere 0xffffff0002bcd400 serv02 kernel: flags () serv02 kernel: v_object 0xffffff0002d22ca8 ref 0 pages 520 serv02 kernel: lock type devfs: EXCL by thread 0xffffff0002956470 (pid 9) serv02 kernel: dev mirror/gmsv02p10.journal serv02 kernel: GEOM_JOURNAL: Cannot suspend file system /home (error=35). pid 9 is the process g_journal switcher and mount gives for /home: /dev/mirror/gmsv02p10.journal on /home (ufs, asynchronous, local, noatime, gjournal) I am aware of on old statement of pjd: it's harmless, it just means journal switch will be done a bit later. Ok, but now I have the same messages on a server running soft updates instead of gjournal during a backup with "dump -L" started by amanda: amandalog: sendbackup: Spawning "/sbin/dump dump 0ubLshf 64 1048576 0 - /dev/amrd0s1f" in pipeline sendbackup: 116: strange(?): mksnap_ffs: Cannot create snapshot /home/.snap/dump_snapshot: Resource temporarily unavailable sendbackup: critical (fatal): error [dump (82637) /sbin/dump returned 1] messages: dsspbx2 kernel: fsync: giving up on dirty dsspbx2 kernel: 0xc5ae4b84: tag devfs, type VCHR dsspbx2 kernel: usecount 1, writecount 0, refcount 123 mountedhere 0xc5a34d00 dsspbx2 kernel: flags () dsspbx2 kernel: v_object 0xc5aeca18 ref 0 pages 834 dsspbx2 kernel: lock type devfs: EXCL by thread 0xc5a4c8a0 (pid 82639) dsspbx2 kernel: dev amrd0s1f dsspbx2 sendbackup[82634]: error [dump (82637) /sbin/dump returned 1] pid 82639 is the process mksnap_ffs and mount gives for /home: /dev/amrd0s1f on /home (ufs, local, noatime, soft-updates) Last year in this list Kirk wrote (for V9) "Note that soft updates without journaling do not show this issue". I like to modify this statement a little bit (for V8) "soft updates do show this is issue, but not so often as gjournal". -- Andreas Longwitz