From owner-freebsd-geom@FreeBSD.ORG Mon Oct 23 11:08:18 2006 Return-Path: X-Original-To: freebsd-geom@FreeBSD.org Delivered-To: freebsd-geom@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 207C516A416 for ; Mon, 23 Oct 2006 11:08:18 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5018443D62 for ; Mon, 23 Oct 2006 11:08:17 +0000 (GMT) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k9NB8H8H027645 for ; Mon, 23 Oct 2006 11:08:17 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k9NB8Fhc027639 for freebsd-geom@FreeBSD.org; Mon, 23 Oct 2006 11:08:15 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 23 Oct 2006 11:08:15 GMT Message-Id: <200610231108.k9NB8Fhc027639@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: linimon set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-geom@FreeBSD.org Cc: Subject: Current problem reports assigned to you 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: Mon, 23 Oct 2006 11:08:18 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/73177 geom kldload geom_* causes panic due to memory exhaustion o kern/76538 geom [gbde] nfs-write on gbde partition stalls and continue o kern/83464 geom [geom] [patch] Unhandled malloc failures within libgeo o kern/84556 geom [geom] GBDE-encrypted swap causes panic at shutdown o kern/87544 geom [gbde] mmaping large files on a gbde filesystem deadlo o kern/89102 geom [geom_vfs] [panic] panic when forced unmount FS from u o bin/90093 geom fdisk(8) incapable of altering in-core geometry o kern/90582 geom [geom_mirror] [panic] Restore cause panic string (ffs_ o kern/98034 geom [geom] dereference of NULL pointer in acd_geom_detach o kern/104389 geom [geom] [patch] sys/geom/geom_dump.c doesn't encode XML 10 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o bin/78131 geom gbde "destroy" not working. o kern/79251 geom [2TB] newfs fails on 2.6TB gbde device o kern/94632 geom [geom] Kernel output resets input while GELI asks for 3 problems total. From owner-freebsd-geom@FreeBSD.ORG Tue Oct 24 15:24:35 2006 Return-Path: X-Original-To: freebsd-geom@FreeBSD.org Delivered-To: freebsd-geom@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD89816A4D4; Tue, 24 Oct 2006 15:24:35 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C60643D8C; Tue, 24 Oct 2006 15:23:55 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id A30B6456B1; Tue, 24 Oct 2006 17:23:43 +0200 (CEST) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 4FCBE45681; Tue, 24 Oct 2006 17:23:35 +0200 (CEST) Date: Tue, 24 Oct 2006 17:23:08 +0200 From: Pawel Jakub Dawidek To: freebsd-geom@FreeBSD.org Message-ID: <20061024152308.GG75746@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Rn7IEEq3VEzCw+ji" Content-Disposition: inline X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-fs@FreeBSD.org Subject: Updated gjournal patches [20061024]. 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: Tue, 24 Oct 2006 15:24:35 -0000 --Rn7IEEq3VEzCw+ji Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi. Patches are at: HEAD: http://people.freebsd.org/~pjd/patches/gjournal_20061024.patch RELENG_6: http://people.freebsd.org/~pjd/patches/gjournal6_20061024.patch Those patches mostly contain build fixes for gconcat and gstripe. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --Rn7IEEq3VEzCw+ji Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFFPi/cForvXbEpPzQRAsQ8AJ4vcJCxQQokxiJd8qCcP4U3zMoEgACg3htt AhjQSPyM28vy4+uLFLjPYOE= =FlYh -----END PGP SIGNATURE----- --Rn7IEEq3VEzCw+ji-- From owner-freebsd-geom@FreeBSD.ORG Tue Oct 24 16:41:31 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 76E1A16A494 for ; Tue, 24 Oct 2006 16:41:31 +0000 (UTC) (envelope-from gcubfg-freebsd-geom@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77D6E43DD1 for ; Tue, 24 Oct 2006 16:40:41 +0000 (GMT) (envelope-from gcubfg-freebsd-geom@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1GcPJe-0005U4-9j for freebsd-geom@freebsd.org; Tue, 24 Oct 2006 18:39:54 +0200 Received: from 89-172-62-134.adsl.net.t-com.hr ([89.172.62.134]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 24 Oct 2006 18:39:50 +0200 Received: from ivoras by 89-172-62-134.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 24 Oct 2006 18:39:50 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-geom@freebsd.org From: Ivan Voras Date: Tue, 24 Oct 2006 18:39:24 +0200 Lines: 7 Message-ID: References: <20061024152308.GG75746@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 89-172-62-134.adsl.net.t-com.hr User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) In-Reply-To: <20061024152308.GG75746@garage.freebsd.pl> Sender: news Subject: Re: Updated gjournal patches [20061024]. 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: Tue, 24 Oct 2006 16:41:31 -0000 Pawel Jakub Dawidek wrote: > Those patches mostly contain build fixes for gconcat and gstripe. As I read it, to play nice with gjournal handlers for BIO_FLUSH should be added to existing GEOM classes, right? (and those are simple bio_clone&send operations, right?) From owner-freebsd-geom@FreeBSD.ORG Tue Oct 24 18:51:02 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DAA4D16A4CE for ; Tue, 24 Oct 2006 18:51:02 +0000 (UTC) (envelope-from antik@bsd.ee) Received: from a5.virtuaal.com (a5.virtuaal.com [195.222.15.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id A22C443D72 for ; Tue, 24 Oct 2006 18:50:59 +0000 (GMT) (envelope-from antik@bsd.ee) Received: from pc134.host2.ida.starman.ee ([62.65.241.134] helo=[192.168.2.100]) by a5.virtuaal.com with esmtpsa (SSLv3:AES256-SHA:256) (Exim 4.52) id 1GcRMX-0003nL-3E for freebsd-geom@freebsd.org; Tue, 24 Oct 2006 21:50:57 +0300 From: Andrei Kolu To: freebsd-geom@freebsd.org Date: Tue, 24 Oct 2006 21:50:54 +0300 User-Agent: KMail/1.9.4 References: <20061024152308.GG75746@garage.freebsd.pl> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200610242150.54923.antik@bsd.ee> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - a5.virtuaal.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - bsd.ee X-Source: X-Source-Args: X-Source-Dir: Subject: Re: Updated gjournal patches [20061024]. 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: Tue, 24 Oct 2006 18:51:02 -0000 On Tuesday 24 October 2006 7:39 pm, Ivan Voras wrote: > Pawel Jakub Dawidek wrote: > > Those patches mostly contain build fixes for gconcat and gstripe. Kernel and world installed just fine, now I have questions: I made some time ago gjournaling filesystem on partition /dev/ad0s3, labeled it, then made ufs filesystem- it worked just great. Later I reformatted this disk to FAT32 filesystem and now I am unable to mount it with gjournal enabled kernel- works fine with "plain" FreeBSD kernel (PC-BSD actually with some config changes). # gjournal label /dev/ad0s3 How can I dejournal this partition and mount it as normal again? Hmm, just changed fstab: /dev/ad0s3.journal /mnt/ad0s3 auto rw,noauto 0 0 Now I can mount it but only as journaled one.... Can I benefit from journaling with other filesystems other than UFS2 right now? Andrei Kolu PC-BSD Quality manager From owner-freebsd-geom@FreeBSD.ORG Tue Oct 24 22:57:57 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC9E316A407 for ; Tue, 24 Oct 2006 22:57:57 +0000 (UTC) (envelope-from antik@bsd.ee) Received: from a5.virtuaal.com (a5.virtuaal.com [195.222.15.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 376D743D4C for ; Tue, 24 Oct 2006 22:57:57 +0000 (GMT) (envelope-from antik@bsd.ee) Received: from pc134.host2.ida.starman.ee ([62.65.241.134] helo=[192.168.2.100]) by a5.virtuaal.com with esmtpsa (SSLv3:AES256-SHA:256) (Exim 4.52) id 1GcVDW-0001DA-AH for freebsd-geom@freebsd.org; Wed, 25 Oct 2006 01:57:54 +0300 From: Andrei Kolu To: freebsd-geom@freebsd.org Date: Wed, 25 Oct 2006 01:57:51 +0300 User-Agent: KMail/1.9.4 References: <20061024152308.GG75746@garage.freebsd.pl> <200610242150.54923.antik@bsd.ee> In-Reply-To: <200610242150.54923.antik@bsd.ee> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200610250157.52139.antik@bsd.ee> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - a5.virtuaal.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - bsd.ee X-Source: X-Source-Args: X-Source-Dir: Subject: Re: Updated gjournal patches [20061024]. 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: Tue, 24 Oct 2006 22:57:57 -0000 I performed performance testing with bonnie++ & blogbench in parallel. # bonnie++ -d /mnt/ad0s4/test -u root -s 8192 -m jump and system freezed on some point and restarted, now I can't mount this partition without fsck-ing first. In /var/log/messages I found this information: Oct 25 01:47:22 PCBSD kernel: WARNING: R/W mount of /mnt/ad0s4 denied. Filesystem is not clean - run fsck Oct 25 01:47:22 PCBSD kernel: WARNING: Expected rawoffset 0, found 113611680 It is usable again after filesystem "cleaning". Why it need fsck- it supposed to be reliable in circumstances like this one? From owner-freebsd-geom@FreeBSD.ORG Wed Oct 25 14:35:30 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 28F3116A416 for ; Wed, 25 Oct 2006 14:35:30 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D41843D69 for ; Wed, 25 Oct 2006 14:35:22 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 87D7E4569A; Wed, 25 Oct 2006 16:35:20 +0200 (CEST) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id BC87A45683; Wed, 25 Oct 2006 16:35:09 +0200 (CEST) Date: Wed, 25 Oct 2006 16:34:46 +0200 From: Pawel Jakub Dawidek To: Andrei Kolu Message-ID: <20061025143446.GE1167@garage.freebsd.pl> References: <20061024152308.GG75746@garage.freebsd.pl> <200610242150.54923.antik@bsd.ee> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="so9zsI5B81VjUb/o" Content-Disposition: inline In-Reply-To: <200610242150.54923.antik@bsd.ee> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-geom@freebsd.org Subject: Re: Updated gjournal patches [20061024]. 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: Wed, 25 Oct 2006 14:35:30 -0000 --so9zsI5B81VjUb/o Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 24, 2006 at 09:50:54PM +0300, Andrei Kolu wrote: > On Tuesday 24 October 2006 7:39 pm, Ivan Voras wrote: > > Pawel Jakub Dawidek wrote: > > > Those patches mostly contain build fixes for gconcat and gstripe. > Kernel and world installed just fine, now I have questions: >=20 > I made some time ago gjournaling filesystem on partition /dev/ad0s3, labe= led=20 > it, then made ufs filesystem- it worked just great. Later I reformatted t= his=20 > disk to FAT32 filesystem and now I am unable to mount it with gjournal=20 > enabled kernel- works fine with "plain" FreeBSD kernel (PC-BSD actually w= ith=20 > some config changes).=20 >=20 > # gjournal label /dev/ad0s3 >=20 > How can I dejournal this partition and mount it as normal again? # gjournal stop ad0s3 # gjournal clear ad0s3 > Hmm, just changed fstab: > /dev/ad0s3.journal /mnt/ad0s3 auto rw,noauto 0 0 >=20 > Now I can mount it but only as journaled one.... Can I benefit from journ= aling=20 > with other filesystems other than UFS2 right now? No. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --so9zsI5B81VjUb/o Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFFP3YGForvXbEpPzQRAgw0AKC5LNiMpKdgbtTaf8xBnl35EB8Z+wCdEPlu DyOZNAgn6JC4C7Rp3I8T54w= =irxv -----END PGP SIGNATURE----- --so9zsI5B81VjUb/o-- From owner-freebsd-geom@FreeBSD.ORG Wed Oct 25 14:36:45 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8714B16A412 for ; Wed, 25 Oct 2006 14:36:45 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FA7443D53 for ; Wed, 25 Oct 2006 14:36:44 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 8AA67456B1; Wed, 25 Oct 2006 16:36:37 +0200 (CEST) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 7BB4345696; Wed, 25 Oct 2006 16:36:26 +0200 (CEST) Date: Wed, 25 Oct 2006 16:36:02 +0200 From: Pawel Jakub Dawidek To: Andrei Kolu Message-ID: <20061025143602.GF1167@garage.freebsd.pl> References: <20061024152308.GG75746@garage.freebsd.pl> <200610242150.54923.antik@bsd.ee> <200610250157.52139.antik@bsd.ee> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vA66WO2vHvL/CRSR" Content-Disposition: inline In-Reply-To: <200610250157.52139.antik@bsd.ee> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-geom@freebsd.org Subject: Re: Updated gjournal patches [20061024]. 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: Wed, 25 Oct 2006 14:36:45 -0000 --vA66WO2vHvL/CRSR Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 25, 2006 at 01:57:51AM +0300, Andrei Kolu wrote: > I performed performance testing with bonnie++ & blogbench in parallel. >=20 > # bonnie++ -d /mnt/ad0s4/test -u root -s 8192 -m jump >=20 > and system freezed on some point and restarted, [...] Is it reproducable? > [...] now I can't mount this=20 > partition without fsck-ing first. In /var/log/messages I found this=20 > information: >=20 > Oct 25 01:47:22 PCBSD kernel: WARNING: R/W mount of /mnt/ad0s4 denied. = =20 > Filesystem is not clean - run fsck > Oct 25 01:47:22 PCBSD kernel: WARNING: Expected rawoffset 0, found 113611= 680 >=20 > It is usable again after filesystem "cleaning". Why it need fsck- it supp= osed=20 > to be reliable in circumstances like this one? You still need to run 'fsck_ffs -p /dev/.journal', but when 'gjournal' option is enabled, it is much, much faster. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --vA66WO2vHvL/CRSR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFFP3ZSForvXbEpPzQRAtwnAKCgEM9kKIVO6E1Uz/4ddSe9KrF09gCgopBo rvJTeh7gdNWD6E8/8xCCPu4= =DVOM -----END PGP SIGNATURE----- --vA66WO2vHvL/CRSR-- From owner-freebsd-geom@FreeBSD.ORG Wed Oct 25 16:36:27 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD23516A412 for ; Wed, 25 Oct 2006 16:36:27 +0000 (UTC) (envelope-from gcubfg-freebsd-geom@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4FD8543D49 for ; Wed, 25 Oct 2006 16:36:25 +0000 (GMT) (envelope-from gcubfg-freebsd-geom@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1GcljA-0001Vu-5M for freebsd-geom@freebsd.org; Wed, 25 Oct 2006 18:35:40 +0200 Received: from 89-172-52-151.adsl.net.t-com.hr ([89.172.52.151]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 25 Oct 2006 18:35:40 +0200 Received: from ivoras by 89-172-52-151.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 25 Oct 2006 18:35:40 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-geom@freebsd.org From: Ivan Voras Date: Wed, 25 Oct 2006 18:35:03 +0200 Lines: 14 Message-ID: References: <20061024152308.GG75746@garage.freebsd.pl> <200610242150.54923.antik@bsd.ee> <20061025143446.GE1167@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 89-172-52-151.adsl.net.t-com.hr User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) In-Reply-To: <20061025143446.GE1167@garage.freebsd.pl> Sender: news Subject: Re: Updated gjournal patches [20061024]. 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: Wed, 25 Oct 2006 16:36:27 -0000 Pawel Jakub Dawidek wrote: > On Tue, Oct 24, 2006 at 09:50:54PM +0300, Andrei Kolu wrote: >> Now I can mount it but only as journaled one.... Can I benefit from journaling >> with other filesystems other than UFS2 right now? > > No. Hmmm. Isn't it more of the case that you CAN benefit from journaling as long as the file system is simple enough (like msdosfs) or you're using it just for the performance and don't mind the fscks (like ext2)? I.e. it's still a generic journaling layer with UFS as a special marginal case, right? From owner-freebsd-geom@FreeBSD.ORG Wed Oct 25 17:27:41 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9EAA16A47C for ; Wed, 25 Oct 2006 17:27:41 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B03E43D6A for ; Wed, 25 Oct 2006 17:27:38 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id D6F4B45B26; Wed, 25 Oct 2006 19:27:36 +0200 (CEST) Received: from localhost (dkz2.neoplus.adsl.tpnet.pl [83.24.29.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 5A8A045696; Wed, 25 Oct 2006 19:27:31 +0200 (CEST) Date: Wed, 25 Oct 2006 19:27:08 +0200 From: Pawel Jakub Dawidek To: Ivan Voras Message-ID: <20061025172707.GA3005@garage.freebsd.pl> References: <20061024152308.GG75746@garage.freebsd.pl> <200610242150.54923.antik@bsd.ee> <20061025143446.GE1167@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YiEDa0DAkWCtVeE4" Content-Disposition: inline In-Reply-To: X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.5 required=3.0 tests=BAYES_00,RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: freebsd-geom@freebsd.org Subject: Re: Updated gjournal patches [20061024]. 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: Wed, 25 Oct 2006 17:27:41 -0000 --YiEDa0DAkWCtVeE4 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 25, 2006 at 06:35:03PM +0200, Ivan Voras wrote: > Pawel Jakub Dawidek wrote: > > On Tue, Oct 24, 2006 at 09:50:54PM +0300, Andrei Kolu wrote: >=20 > >> Now I can mount it but only as journaled one.... Can I benefit from jo= urnaling=20 > >> with other filesystems other than UFS2 right now? > >=20 > > No. >=20 > Hmmm. Isn't it more of the case that you CAN benefit from journaling as > long as the file system is simple enough (like msdosfs) or you're using > it just for the performance and don't mind the fscks (like ext2)? >=20 > I.e. it's still a generic journaling layer with UFS as a special > marginal case, right? That's right. There can be performance benefits, but one has to verify this in specific workload. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --YiEDa0DAkWCtVeE4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFFP55rForvXbEpPzQRApGhAJ9GLUgYMSammcm8+IldTHXUMECB+gCgsiCo hsZScRM5L7N9P7rPf77DUU8= =48Li -----END PGP SIGNATURE----- --YiEDa0DAkWCtVeE4-- From owner-freebsd-geom@FreeBSD.ORG Thu Oct 26 16:32:42 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2CD4D16A403 for ; Thu, 26 Oct 2006 16:32:42 +0000 (UTC) (envelope-from antik@bsd.ee) Received: from a5.virtuaal.com (a5.virtuaal.com [195.222.15.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3AF8143D68 for ; Thu, 26 Oct 2006 16:32:38 +0000 (GMT) (envelope-from antik@bsd.ee) Received: from pc134.host2.ida.starman.ee ([62.65.241.134] helo=[192.168.2.100]) by a5.virtuaal.com with esmtpsa (SSLv3:AES256-SHA:256) (Exim 4.52) id 1Gd89i-00005g-39 for freebsd-geom@freebsd.org; Thu, 26 Oct 2006 19:32:34 +0300 From: Andrei Kolu To: freebsd-geom@freebsd.org Date: Thu, 26 Oct 2006 19:32:35 +0300 User-Agent: KMail/1.9.4 References: <20061024152308.GG75746@garage.freebsd.pl> <20061025143446.GE1167@garage.freebsd.pl> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200610261932.35945.antik@bsd.ee> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - a5.virtuaal.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - bsd.ee X-Source: X-Source-Args: X-Source-Dir: Subject: gjournaled UFS2 filesystem is gone after power outage 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, 26 Oct 2006 16:32:42 -0000 I got power outage- UPS couldn't handle it this time- have to replace battery and now I can't read my filesystem that I made for testing purposes: # mount /dev/ad0s4.journal /mnt/ad0s4/ mount: /dev/ad0s4.journal: Operation not permitted # fsck /dev/ad0s4 fsck: Could not determine filesystem type /var/log/messages: Oct 26 19:28:01 PCBSD kernel: WARNING: R/W mount of /mnt/ad0s4 denied. Filesystem is not clean - run fsck Oct 26 19:28:01 PCBSD kernel: WARNING: Expected rawoffset 0, found 113611680 From owner-freebsd-geom@FreeBSD.ORG Thu Oct 26 17:44:48 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 49E9C16A403 for ; Thu, 26 Oct 2006 17:44:48 +0000 (UTC) (envelope-from etc@fluffles.net) Received: from auriate.fluffles.net (a83-68-3-169.adsl.cistron.nl [83.68.3.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id D902443D55 for ; Thu, 26 Oct 2006 17:44:47 +0000 (GMT) (envelope-from etc@fluffles.net) Received: from destiny ([10.0.0.21]) by auriate.fluffles.net with esmtpa (Exim 4.63 (FreeBSD)) (envelope-from ) id 1Gd9HZ-000573-Tg; Thu, 26 Oct 2006 19:44:45 +0200 Message-ID: <4540F40C.2000302@fluffles.net> Date: Thu, 26 Oct 2006 19:44:44 +0200 From: Fluffles User-Agent: Thunderbird 1.5.0.7 (X11/20060917) MIME-Version: 1.0 To: freebsd-geom@freebsd.org References: <20061024152308.GG75746@garage.freebsd.pl> <20061025143446.GE1167@garage.freebsd.pl> <200610261932.35945.antik@bsd.ee> In-Reply-To: <200610261932.35945.antik@bsd.ee> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Andrei Kolu Subject: Re: gjournaled UFS2 filesystem is gone after power outage 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, 26 Oct 2006 17:44:48 -0000 Andrei Kolu wrote: > I got power outage- UPS couldn't handle it this time- have to replace battery > and now I can't read my filesystem that I made for testing purposes: > > # mount /dev/ad0s4.journal /mnt/ad0s4/ > mount: /dev/ad0s4.journal: Operation not permitted > # fsck /dev/ad0s4 > fsck: Could not determine filesystem type > Well you should use: fsck -t ufs /dev/ad0s4 and after that mount it. Right now you should be able to mount the volume with mount -f /dev/ad0s4 , but that is not recommended. But i were told fsck was not necessary when using gjournal. *shrug* From owner-freebsd-geom@FreeBSD.ORG Thu Oct 26 19:35:10 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8D83316A417 for ; Thu, 26 Oct 2006 19:35:10 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id D23D943D53 for ; Thu, 26 Oct 2006 19:35:09 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id F3E6E487F4; Thu, 26 Oct 2006 21:35:07 +0200 (CEST) Received: from localhost (dkd232.neoplus.adsl.tpnet.pl [83.24.7.232]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id ACC72487F0; Thu, 26 Oct 2006 21:35:02 +0200 (CEST) Date: Thu, 26 Oct 2006 21:34:37 +0200 From: Pawel Jakub Dawidek To: Fluffles Message-ID: <20061026193437.GA9491@garage.freebsd.pl> References: <20061024152308.GG75746@garage.freebsd.pl> <20061025143446.GE1167@garage.freebsd.pl> <200610261932.35945.antik@bsd.ee> <4540F40C.2000302@fluffles.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ew6BAiZeqk4r7MaW" Content-Disposition: inline In-Reply-To: <4540F40C.2000302@fluffles.net> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.5 required=3.0 tests=BAYES_00,RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: Andrei Kolu , freebsd-geom@freebsd.org Subject: Re: gjournaled UFS2 filesystem is gone after power outage 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, 26 Oct 2006 19:35:10 -0000 --ew6BAiZeqk4r7MaW Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 26, 2006 at 07:44:44PM +0200, Fluffles wrote: > Andrei Kolu wrote: > > I got power outage- UPS couldn't handle it this time- have to replace b= attery=20 > > and now I can't read my filesystem that I made for testing purposes: > > > > # mount /dev/ad0s4.journal /mnt/ad0s4/ > > mount: /dev/ad0s4.journal: Operation not permitted > > # fsck /dev/ad0s4 > > fsck: Could not determine filesystem type > > =20 >=20 > Well you should use: >=20 > fsck -t ufs /dev/ad0s4 > and after that mount it. >=20 > Right now you should be able to mount the volume with mount -f > /dev/ad0s4 , but that is not recommended. >=20 > But i were told fsck was not necessary when using gjournal. *shrug* 'fsck_ffs -p /dev/ad0s4.journal' is needed, but it only handles orphaned files, which takes seconds, not hours. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --ew6BAiZeqk4r7MaW Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFFQQ3NForvXbEpPzQRAojsAJ4iKgbbxS08gTDtV5jL6Np0blR10QCeOwmo oTJAIRVZf/Of2hLgUEWbIoQ= =pXbr -----END PGP SIGNATURE----- --ew6BAiZeqk4r7MaW-- From owner-freebsd-geom@FreeBSD.ORG Thu Oct 26 20:14:45 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA45E16A47C for ; Thu, 26 Oct 2006 20:14:45 +0000 (UTC) (envelope-from antik@bsd.ee) Received: from a5.virtuaal.com (a5.virtuaal.com [195.222.15.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 372D843D4C for ; Thu, 26 Oct 2006 20:14:45 +0000 (GMT) (envelope-from antik@bsd.ee) Received: from pc134.host2.ida.starman.ee ([62.65.241.134] helo=[192.168.2.100]) by a5.virtuaal.com with esmtpsa (SSLv3:AES256-SHA:256) (Exim 4.52) id 1GdBch-0006YY-2s for freebsd-geom@freebsd.org; Thu, 26 Oct 2006 23:14:43 +0300 From: Andrei Kolu To: freebsd-geom@freebsd.org Date: Thu, 26 Oct 2006 23:14:45 +0300 User-Agent: KMail/1.9.4 References: <20061024152308.GG75746@garage.freebsd.pl> <4540F40C.2000302@fluffles.net> <20061026193437.GA9491@garage.freebsd.pl> In-Reply-To: <20061026193437.GA9491@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200610262314.45754.antik@bsd.ee> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - a5.virtuaal.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - bsd.ee X-Source: X-Source-Args: X-Source-Dir: Subject: Re: gjournaled UFS2 filesystem is gone after power outage 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, 26 Oct 2006 20:14:45 -0000 On Thursday 26 October 2006 10:34 pm, Pawel Jakub Dawidek wrote: > On Thu, Oct 26, 2006 at 07:44:44PM +0200, Fluffles wrote: > > Andrei Kolu wrote: > > > I got power outage- UPS couldn't handle it this time- have to replace > > > battery and now I can't read my filesystem that I made for testing > > > purposes: > > > > > > # mount /dev/ad0s4.journal /mnt/ad0s4/ > > > mount: /dev/ad0s4.journal: Operation not permitted > > > # fsck /dev/ad0s4 > > > fsck: Could not determine filesystem type > > > > Well you should use: > > > > fsck -t ufs /dev/ad0s4 > > and after that mount it. > > > > Right now you should be able to mount the volume with mount -f > > /dev/ad0s4 , but that is not recommended. > > > > But i were told fsck was not necessary when using gjournal. *shrug* > > 'fsck_ffs -p /dev/ad0s4.journal' is needed, but it only handles orphaned > files, which takes seconds, not hours. Can I enable background check or at least automatic one? I always forgot to add .journal extension. From owner-freebsd-geom@FreeBSD.ORG Thu Oct 26 21:11:26 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA18C16A403 for ; Thu, 26 Oct 2006 21:11:26 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F90C43D45 for ; Thu, 26 Oct 2006 21:11:25 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id C1F0F45696; Thu, 26 Oct 2006 23:11:24 +0200 (CEST) Received: from localhost (dkd232.neoplus.adsl.tpnet.pl [83.24.7.232]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id CE34A45681; Thu, 26 Oct 2006 23:11:19 +0200 (CEST) Date: Thu, 26 Oct 2006 23:10:54 +0200 From: Pawel Jakub Dawidek To: Andrei Kolu Message-ID: <20061026211054.GB9491@garage.freebsd.pl> References: <20061024152308.GG75746@garage.freebsd.pl> <4540F40C.2000302@fluffles.net> <20061026193437.GA9491@garage.freebsd.pl> <200610262314.45754.antik@bsd.ee> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zx4FCpZtqtKETZ7O" Content-Disposition: inline In-Reply-To: <200610262314.45754.antik@bsd.ee> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.5 required=3.0 tests=BAYES_00,RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: freebsd-geom@freebsd.org Subject: Re: gjournaled UFS2 filesystem is gone after power outage 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, 26 Oct 2006 21:11:27 -0000 --zx4FCpZtqtKETZ7O Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 26, 2006 at 11:14:45PM +0300, Andrei Kolu wrote: > On Thursday 26 October 2006 10:34 pm, Pawel Jakub Dawidek wrote: > > On Thu, Oct 26, 2006 at 07:44:44PM +0200, Fluffles wrote: > > > Andrei Kolu wrote: > > > > I got power outage- UPS couldn't handle it this time- have to repla= ce > > > > battery and now I can't read my filesystem that I made for testing > > > > purposes: > > > > > > > > # mount /dev/ad0s4.journal /mnt/ad0s4/ > > > > mount: /dev/ad0s4.journal: Operation not permitted > > > > # fsck /dev/ad0s4 > > > > fsck: Could not determine filesystem type > > > > > > Well you should use: > > > > > > fsck -t ufs /dev/ad0s4 > > > and after that mount it. > > > > > > Right now you should be able to mount the volume with mount -f > > > /dev/ad0s4 , but that is not recommended. > > > > > > But i were told fsck was not necessary when using gjournal. *shrug* > > > > 'fsck_ffs -p /dev/ad0s4.journal' is needed, but it only handles orphaned > > files, which takes seconds, not hours. >=20 > Can I enable background check or at least automatic one? I always forgot = to=20 > add .journal extension.=20 It will be automatically checked if you have it in /etc/fstab. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --zx4FCpZtqtKETZ7O Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFFQSReForvXbEpPzQRAibCAJoCZMCetqXo+f8fWKWxmFXBAPRqIwCfQUJq MtYtttJXpKBF42Fv5iljZOQ= =d5IJ -----END PGP SIGNATURE----- --zx4FCpZtqtKETZ7O-- From owner-freebsd-geom@FreeBSD.ORG Fri Oct 27 12:16:20 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C55F16A407; Fri, 27 Oct 2006 12:16:20 +0000 (UTC) (envelope-from nik@optim.com.ru) Received: from mail.optim-mol.cemu.ru (mail.optim-mol.cemu.ru [83.102.188.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7537B43D60; Fri, 27 Oct 2006 12:16:10 +0000 (GMT) (envelope-from nik@optim.com.ru) Received: from [192.168.2.254] (user-0cet49q.cable.mindspring.com [24.238.145.58]) (authenticated bits=0) by mail.optim-mol.cemu.ru (8.13.8/8.13.8) with ESMTP id k9RCG0pF016656 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 27 Oct 2006 16:16:05 +0400 (MSD) (envelope-from nik@optim.com.ru) Message-ID: <4541F88D.6080201@optim.com.ru> Date: Fri, 27 Oct 2006 07:16:13 -0500 From: Nikolay Mirin Organization: =?KOI8-R?Q?=EF=F0=F4=E9=ED?= User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: freebsd-geom@freebsd.org, freebsd-questions@freebsd.org Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-92.8 required=5.0 tests=RCVD_IN_DSBL, RCVD_IN_NJABL_DUL,RCVD_IN_NJABL_PROXY,RCVD_IN_SORBS_DUL,SPF_FAIL, USER_IN_WHITELIST autolearn=disabled version=3.1.4 X-Spam-Checker-Version: SpamAssassin 3.1.4 (2006-07-25) on mail.optim-mol.cemu.ru Cc: Subject: Re: GELI provider would never detach problem solution 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, 27 Oct 2006 12:16:20 -0000 The problem has been fixed temporarily! Here is the PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=104669 This is a bug, indeed, however. From owner-freebsd-geom@FreeBSD.ORG Fri Oct 27 12:25:39 2006 Return-Path: X-Original-To: freebsd-geom@FreeBSD.org Delivered-To: freebsd-geom@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C907816A412; Fri, 27 Oct 2006 12:25:39 +0000 (UTC) (envelope-from etc@fluffles.net) Received: from auriate.fluffles.net (a83-68-3-169.adsl.cistron.nl [83.68.3.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6738043D45; Fri, 27 Oct 2006 12:25:39 +0000 (GMT) (envelope-from etc@fluffles.net) Received: from destiny ([10.0.0.21]) by auriate.fluffles.net with esmtpa (Exim 4.63 (FreeBSD)) (envelope-from ) id 1GdQmI-000CgR-9f; Fri, 27 Oct 2006 14:25:38 +0200 Message-ID: <4541FAC1.1000601@fluffles.net> Date: Fri, 27 Oct 2006 14:25:37 +0200 From: Fluffles User-Agent: Thunderbird 1.5.0.7 (X11/20060917) MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <20061024152308.GG75746@garage.freebsd.pl> In-Reply-To: <20061024152308.GG75746@garage.freebsd.pl> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org, freebsd-geom@FreeBSD.org Subject: Re: Updated gjournal patches [20061024]. 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, 27 Oct 2006 12:25:39 -0000 Hi Pawel, I've tried your recent (20061024) gjournal patches on my test fileserver, which is an amd64 FreeBSD7 box with 8 SATA disks. I'm currently using graid5 on it, with success. I've also tried using gjournal, but with little success. The compilation/installation and creation of the journal device goes as planned, but i get kernel panics not long after i start writing to it. A "newfs -b 65536 /dev/raid5/sophia.journal" quickly panicked the system. After that i tried without the -b parameter; that appeared to work but not long after i got a panic again; same panic as before. Please look at the screenshot i made of the panic message: http://dev.fluffles.net/images/gjournal-panic1.png Do you know what could be causing the panic? The panic message itself is not very explanatory. ;-) Perhaps gjournal doesn't play nice with graid5? I haven't tried it on a single disk, yet. Also i have a question about it's performance. You mentioned earlier that writing big files takes about twice as long with gjournal, i wonder if this is inherit to journaling itself or due to the current implementation. Windows' journaling NTFS, for example, isn't slower than FAT32 with big files if i remember correctly. What major differences in the journaling process causes this? Also, in your earlier post you explained the advantages of a journal with regard to significantly reduces fsck times at boot. But my major concern is dataloss: on my testserver i've had many kernel panics/freezes due to the experimental graid5 module being tested by Arne. This has resulted in the system not being able to boot because the ad0s2a (read: a!) partition has lost files. And it won't be the first time a lockup or power failure caused dataloss on my systems. That's why i want to use gjournal: to protect from dataloss. Am i correct in my assumption that gjournal addresses my needs in this regard? Greetings, Veronica From owner-freebsd-geom@FreeBSD.ORG Fri Oct 27 13:27:16 2006 Return-Path: X-Original-To: freebsd-geom@FreeBSD.org Delivered-To: freebsd-geom@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7066516A4D2; Fri, 27 Oct 2006 13:27:16 +0000 (UTC) (envelope-from etc@fluffles.net) Received: from auriate.fluffles.net (a83-68-3-169.adsl.cistron.nl [83.68.3.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 512A043DC4; Fri, 27 Oct 2006 13:25:57 +0000 (GMT) (envelope-from etc@fluffles.net) Received: from destiny ([10.0.0.21]) by auriate.fluffles.net with esmtpa (Exim 4.63 (FreeBSD)) (envelope-from ) id 1GdRiR-000D1O-Bb; Fri, 27 Oct 2006 15:25:43 +0200 Message-ID: <454208D6.7000006@fluffles.net> Date: Fri, 27 Oct 2006 15:25:42 +0200 From: Fluffles User-Agent: Thunderbird 1.5.0.7 (X11/20060917) MIME-Version: 1.0 To: Fluffles References: <20061024152308.GG75746@garage.freebsd.pl> <4541FAC1.1000601@fluffles.net> In-Reply-To: <4541FAC1.1000601@fluffles.net> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org, Pawel Jakub Dawidek , freebsd-geom@FreeBSD.org Subject: Re: Updated gjournal patches [20061024]. 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, 27 Oct 2006 13:27:16 -0000 Addendum: i tried gjournal on a single disk now without any GEOM layers on it, but it still crashes with the same error. - Veronica Fluffles wrote: > Hi Pawel, > > I've tried your recent (20061024) gjournal patches on my test > fileserver, which is an amd64 FreeBSD7 box with 8 SATA disks. I'm > currently using graid5 on it, with success. > I've also tried using gjournal, but with little success. The > compilation/installation and creation of the journal device goes as > planned, but i get kernel panics not long after i start writing to it. A > "newfs -b 65536 /dev/raid5/sophia.journal" quickly panicked the system. > After that i tried without the -b parameter; that appeared to work but > not long after i got a panic again; same panic as before. > > Please look at the screenshot i made of the panic message: > http://dev.fluffles.net/images/gjournal-panic1.png > > Do you know what could be causing the panic? The panic message itself is > not very explanatory. ;-) > Perhaps gjournal doesn't play nice with graid5? I haven't tried it on a > single disk, yet. > > Also i have a question about it's performance. You mentioned earlier > that writing big files takes about twice as long with gjournal, i wonder > if this is inherit to journaling itself or due to the current > implementation. Windows' journaling NTFS, for example, isn't slower than > FAT32 with big files if i remember correctly. What major differences in > the journaling process causes this? > > Also, in your earlier post you explained the advantages of a journal > with regard to significantly reduces fsck times at boot. But my major > concern is dataloss: on my testserver i've had many kernel > panics/freezes due to the experimental graid5 module being tested by > Arne. This has resulted in the system not being able to boot because the > ad0s2a (read: a!) partition has lost files. And it won't be the first > time a lockup or power failure caused dataloss on my systems. That's why > i want to use gjournal: to protect from dataloss. Am i correct in my > assumption that gjournal addresses my needs in this regard? > > Greetings, > > Veronica > _______________________________________________ > freebsd-geom@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-geom > To unsubscribe, send any mail to "freebsd-geom-unsubscribe@freebsd.org" > > > From owner-freebsd-geom@FreeBSD.ORG Fri Oct 27 14:46:15 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B3AE216A416 for ; Fri, 27 Oct 2006 14:46:15 +0000 (UTC) (envelope-from gcubfg-freebsd-geom@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5727743D73 for ; Fri, 27 Oct 2006 14:46:13 +0000 (GMT) (envelope-from gcubfg-freebsd-geom@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1GdSuY-0001xk-6A for freebsd-geom@freebsd.org; Fri, 27 Oct 2006 16:42:18 +0200 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 27 Oct 2006 16:42:18 +0200 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 27 Oct 2006 16:42:18 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-geom@freebsd.org From: Ivan Voras Date: Fri, 27 Oct 2006 16:38:05 +0200 Lines: 88 Message-ID: References: <20061024152308.GG75746@garage.freebsd.pl> <4541FAC1.1000601@fluffles.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 1.5.0.4 (X11/20060625) In-Reply-To: <4541FAC1.1000601@fluffles.net> Sender: news Cc: freebsd-fs@freebsd.org Subject: Re: Updated gjournal patches [20061024]. 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, 27 Oct 2006 14:46:15 -0000 Fluffles wrote: > Please look at the screenshot i made of the panic message: > http://dev.fluffles.net/images/gjournal-panic1.png Hmm, quick grepping of the kernel sources for "Enough\." and sources for gjournal and graid5 for other strings in the panic screenshot doesn't locate a possible point of failure. You'll probably need to at least compile DDB & KDB into the kernel so when the panic happens you can create a backtrace (with "bt" command) and post that information. > Also i have a question about it's performance. You mentioned earlier > that writing big files takes about twice as long with gjournal, i wonder > if this is inherit to journaling itself or due to the current > implementation. Windows' journaling NTFS, for example, isn't slower than > FAT32 with big files if i remember correctly. What major differences in > the journaling process causes this? Maybe MS is doing its tricks again? The way any journaling works is this: data is not written where it's supposed to be (which is all over the disk because files and metadata are scattered across the disk), but its written in a special on-disk area which is designated "the journal" and which is sequential. After some time (e.g. when the I/O load decreases) the data is read from the journal and written to where it belongs. Thus burst writes to file system are very fast, and the slow operations (data "relocation" to where it belongs) is performed when system is under less load. This journal area is finite in size, so when it gets full, no more writes can happen until at least part of it is "freed" by relocating the data where it belongs, which is an operation that requires sequential reading from journal area and scattered writing to the on-disk data area. When large files are written to the file system "in bulk", the FS is already smart enough to store them as sequentially as possible, but there are two problems with it: - the FS can't reliably detect if the file that's going to be written is sequential or not, and neither can the journal driver (so the FS actually does best effort for any file in the hope that if the file grows large enough it won't get fragmented) - all FS operations go through gjournal, so the sequence of operations becomes: 1. data is written to the journal, 2. the journal gets full and data is read again from the journal and written to where it belongs, and during this new writes to the journal are at best very slow. Thus the slowdown. > Also, in your earlier post you explained the advantages of a journal > with regard to significantly reduces fsck times at boot. But my major > concern is dataloss: on my testserver i've had many kernel > panics/freezes due to the experimental graid5 module being tested by > Arne. This has resulted in the system not being able to boot because the > ad0s2a (read: a!) partition has lost files. And it won't be the first > time a lockup or power failure caused dataloss on my systems. That's why > i want to use gjournal: to protect from dataloss. Am i correct in my > assumption that gjournal addresses my needs in this regard? To guarantee (meta)data safety on the file system, the FS code must be sure the data it has placed on the disk will stay there. Soft updates work so data is written in order and in batches, and the code assumes each such "batch" arrives safely on the hardware. SU's performance comes from delaying writes with the intention of not rewriting the same data multiple times (consider deleting a huge number of files from a directory: the same directory entry SHOULD be updated after each delete, but SU delays it so only the final version of the directory, with removed files, is written). Journaling on the other hand works by allowing each such write to proceed to the disk, BUT instead of seeking every time to accommodate where the data is placed, it writes all data sequentially on the journal, which is much faster (60+ MB/s with today's hardware). Smart journal engines (don't know if gjournal has this feature) will only relocate the last modified data entry (e.g. the last "state" of the directory entry from the example with SU) to its place. Because all the intermediate data from the file system is placed in the journal, a power drop in the middle of updating a directory entry will result in either the directory entry being safely written to the journal (from where it can be recovered), or the changes being completely lost (in which case the old, un-updated directory entry is still valid). In all this, gjournal should do what you need. The biggest problem today is not the software, but the hardware. Most disk drives (especially desktop-class ones) lie about safely writing the data when it's still in their buffers. This is why the modern approach to building critical data storage is to force the drives not to cache anything, and employ a hardware RAID controller with huge buffers and a battery that keeps the buffers "alive" when the power goes down.