From owner-freebsd-hackers@FreeBSD.ORG Sat Aug 26 02:22:28 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B90816A4DD for ; Sat, 26 Aug 2006 02:22:28 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C9AF43D4C for ; Sat, 26 Aug 2006 02:22:27 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.24] (andersonbox4.centtech.com [192.168.42.24]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k7Q2MRcp041048 for ; Fri, 25 Aug 2006 21:22:27 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <44EFB062.5090708@centtech.com> Date: Fri, 25 Aug 2006 21:22:26 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5.0.5 (X11/20060802) MIME-Version: 1.0 To: FreeBSD Hackers Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1729/Fri Aug 25 12:57:01 2006 on mh2.centtech.com X-Virus-Status: Clean Subject: fsync: giving up on dirty X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Aug 2006 02:22:28 -0000 I got this error today, while some very heavy disk access was occurring: Aug 25 13:47:07 snapshot1 kernel: fsync: giving up on dirty Aug 25 13:47:07 snapshot1 kernel: 0xffffff01bbb99a20: tag devfs, type VCHR Aug 25 13:47:07 snapshot1 kernel: usecount 1, writecount 0, refcount 445 mountedhere 0xffffff023ee20800 Aug 25 13:47:07 snapshot1 kernel: flags () Aug 25 13:47:07 snapshot1 kernel: v_object 0xffffff01c34afb60 ref 0 pages 16386 Aug 25 13:47:07 snapshot1 kernel: lock type devfs: EXCL (count 1) by thread 0xffffff023f11d980 (pid 46)#0 0xffffffff803eeaa6 at lockmgr+0x5f6 Aug 25 13:47:07 snapshot1 kernel: #1 0xffffffff8065e8d1 at VOP_LOCK_APV+0x81 Aug 25 13:47:07 snapshot1 kernel: #2 0xffffffff8047015b at vn_lock+0x6b Aug 25 13:47:07 snapshot1 kernel: #3 0xffffffff805719be at ffs_sync+0x1fe Aug 25 13:47:07 snapshot1 kernel: #4 0xffffffff80472045 at vfs_write_suspend+0x95 Aug 25 13:47:07 snapshot1 kernel: #5 0xffffffff80b794a5 at g_journal_switcher+0xa55 Aug 25 13:47:07 snapshot1 kernel: #6 0xffffffff803e3cdb at fork_exit+0xbb Aug 25 13:47:07 snapshot1 kernel: #7 0xffffffff805f39ce at fork_trampoline+0xe Aug 25 13:47:07 snapshot1 kernel: Aug 25 13:47:07 snapshot1 kernel: dev label/vol11-data.journal Aug 25 13:47:07 snapshot1 kernel: GEOM_JOURNAL: Cannot suspend file system /vol11 (error=35). Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------