From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 08:37:12 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1595E16A468 for ; Thu, 1 Nov 2007 08:37:12 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: from corpmail.itlegion.ru (corpmail.itlegion.ru [84.21.226.211]) by mx1.freebsd.org (Postfix) with SMTP id EB58613C48D for ; Thu, 1 Nov 2007 08:37:10 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: (qmail 3897 invoked from network); 31 Oct 2007 22:04:51 +0300 Received: from unknown (HELO Artem) (192.168.0.12) by 84.21.226.211 with SMTP; 31 Oct 2007 22:04:51 +0300 X-AntiVirus: Checked by Dr.Web [version: 4.44, engine: 4.44.0.09170, virus records: 253189, updated: 31.10.2007] Message-ID: <004801c81bf0$e7bec7c0$0c00a8c0@Artem> From: "Artem Kuchin" To: "Pawel Jakub Dawidek" References: <00f101c819f7$833d5370$0c00a8c0@Artem> <20071031095213.GG8068@garage.freebsd.pl> <02af01c81bb9$7f7828a0$0c00a8c0@Artem> <20071031183838.GB13180@garage.freebsd.pl> <001b01c81bef$54805790$0c00a8c0@Artem> <20071031185826.GC13180@garage.freebsd.pl> Date: Wed, 31 Oct 2007 22:04:23 +0300 Organization: IT Legion MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="ISO-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Cc: freebsd-current@freebsd.org Subject: Re: Problems with gjournal or something else. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 08:37:12 -0000 >> My point here is that since it is and example of configuring a gjournaling >> onf >> existing system then this 'gjournal label da0s1d da0s1e' will always fail. > >No. It will fail only if your file system is using the last sector. UFS >operates on fragments, so if your disk/slice/partition is not >fragment-aligned it will work. So, i shoot myself in a foot and got all those error=5 because in my case i put journal in the same fs and cut 1GB of data from it, right? >> Of course it says the warning, but basically, condidering that it overwrites >> last sector+1 GB of data on existing FS there is actual configuring on >> existing FS. It is simply destroying it. >The example is using separate provider (da0s1e) for the journal, so it >only needs one sector from da0s1d. Ah! i see. What about porper journal size? Any recommendations? Also, please, take a look at "BIO_FLUSH on twe driver" thread. -- Artem