From owner-freebsd-geom@FreeBSD.ORG Fri Mar 7 09:56:30 2008 Return-Path: Delivered-To: freebsd-geom@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6B8BB1065676 for ; Fri, 7 Mar 2008 09:56:30 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [91.103.162.4]) by mx1.freebsd.org (Postfix) with ESMTP id 2B05C8FC16 for ; Fri, 7 Mar 2008 09:56:29 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from localhost (localhost.codelab.cz [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 8DF2019E023 for ; Fri, 7 Mar 2008 10:39:33 +0100 (CET) Received: from [192.168.1.2] (r5bb235.net.upc.cz [86.49.61.235]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTP id 4361D19E019 for ; Fri, 7 Mar 2008 10:39:29 +0100 (CET) Message-ID: <47D10D60.3010207@quip.cz> Date: Fri, 07 Mar 2008 10:39:44 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: cz, cs, en, en-us MIME-Version: 1.0 To: freebsd-geom@FreeBSD.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: GEOM_JOURNAL: Cannot suspend file system /vol0 (error=35) X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Mar 2008 09:56:30 -0000 Hi, today I saw this error in messages: : fsync: giving up on dirty : 0xc5564110: tag devfs, type VCHR : usecount 1, writecount 0, refcount 78 mountedhere 0xc54ef800 : flags () : v_object 0xc556645c ref 0 pages 1146 : lock type devfs: EXCL (count 1) by thread 0xc5236a50 (pid 39) : dev mirror/gm0s2e.journal : GEOM_JOURNAL: Cannot suspend file system /vol0 (error=35). Is it something harmful, or is it "normal" behavior? It was in time when generating backup (high disk I/O). Gjournal is on top of gmirrored SATA disks. mirror/gm0s2d is 2GB journal provider mirror/gm0s2e.journal is 380GB data provider Miroslav Lachman