From owner-freebsd-geom@FreeBSD.ORG Thu Mar 10 09:31:26 2011 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 917A01065672 for ; Thu, 10 Mar 2011 09:31:26 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id 715978FC18 for ; Thu, 10 Mar 2011 09:31:26 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id p2A9VM5p051970 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 10 Mar 2011 01:31:22 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id p2A9VMeW051966; Thu, 10 Mar 2011 01:31:22 -0800 (PST) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA28568; Thu, 10 Mar 11 01:22:38 PST Date: Thu, 10 Mar 2011 01:22:40 -0800 From: perryh@pluto.rain.com To: hugo@barafranca.com Message-Id: <4d789860.paJTjyqMw4MoO+3i%perryh@pluto.rain.com> References: <4D77780F.8020209@barafranca.com> In-Reply-To: <4D77780F.8020209@barafranca.com> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-geom@freebsd.org Subject: Re: Cannot create gjournal on gmirror partition - 8.2-RELEASE: "No such file or directory" 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: Thu, 10 Mar 2011 09:31:26 -0000 Hugo Silva wrote: > gm0s1h is a 1.4T partition ... > > While attempting to create a gjournal there: > # gjournal label /dev/mirror/gm0s1h > gjournal: Cannot clear metadata on /dev/mirror/gm0s1h: No such file or > directory. One problem is that "gjournal label /dev/mirror/gm0s1h" (specifying only one provider) asks gjournal to create the journal on the same provider which holds the data. That only works if the provider is empty. (However I don't know whether that is the cause of the particular message you're getting.) > Another thing: We've noticed that system becomes very unresponsive > x.. while bgfsck is running on that big partition. However, the > same doesn't happen while gmirror is syncing, at 80MB/s. Does > anyone know why one operation (fsck on huge partition) impacts the > systems performance so much, while another (gmirror sync) does not? I would hazard a guess that your system is memory constrained, and that fsck's working set -- especially when running on a very large partition -- is considerably larger than what's needed to perform a simple data-copy operation to sync a mirror. Adding more memory might help.