From owner-freebsd-questions@FreeBSD.ORG Sat Apr 19 04:18:55 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B3C55106566B for ; Sat, 19 Apr 2008 04:18:55 +0000 (UTC) (envelope-from unga888@yahoo.com) Received: from web57009.mail.re3.yahoo.com (web57009.mail.re3.yahoo.com [66.196.97.113]) by mx1.freebsd.org (Postfix) with SMTP id 787678FC0C for ; Sat, 19 Apr 2008 04:18:55 +0000 (UTC) (envelope-from unga888@yahoo.com) Received: (qmail 84831 invoked by uid 60001); 19 Apr 2008 04:18:54 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=uJJx4fGkBa3ivbg7NuXORAYFKsqx4ndBKuDdv9QtdapoSKqu2457AFG3QD2oXOjZB6t1thsKftp65qY1UqkQu7GEy7TiyzvCWE27BHdXNkJP5VVkHWnjj6mboHStFuEfP0MYNkHJ9eRbKzydHOxNmdoy/rGOaq1VBY7qhzg6lmc=; X-YMail-OSG: 0Re8hvIVM1kKENCdzMz41hGrSQxidjb4nI9gU_s9D6RftdugzJCgrNnV.NKzfbheRB6OmB_S4xpjkAYQTIwiJiBfOWzdaP7sjJuPBq4d1KVudDbVmbV3fWAPV2w- Received: from [165.21.155.13] by web57009.mail.re3.yahoo.com via HTTP; Fri, 18 Apr 2008 21:18:54 PDT Date: Fri, 18 Apr 2008 21:18:54 -0700 (PDT) From: Unga To: freebsd-questions@freebsd.org In-Reply-To: <9bbcef730804180840y77adff73x7ad0cf90c82633a9@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <759748.83603.qm@web57009.mail.re3.yahoo.com> Cc: Ivan Voras Subject: Re: UFS2 Journaling implementation detail X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Apr 2008 04:18:55 -0000 --- Ivan Voras wrote: > > Does it log anywhere if the journal size is too > small for the system load? > > Yes, you'll get a system panic in this case. Yes, > it's a bad solution, complain to Pawel :) > So the gjournal can corrupt the file system as well as can fix it :) I think this is a serious concern for desktop users rather than servers. For those who do multi-channel audio encoding, HD/35mm-full-frame video encoding, batch conversion of photos, etc. may hit the default 1GB journal size and end up in system panic. I think because of this gjournal implementation issue, gjournal requires a huge journal. Just for a thought, in my opinion, gjournal should not use the entire journal for logging. May be split it two. Ie. From size S given, use two journals. When one journal is full, point the new changes to go to the second journal, and flush the first journal and so on. If the gjournal has to flush too often, then log it in the system log that journal is too small. Ivan, thanks again for detail. Kind regards Unga ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ