From owner-freebsd-stable@FreeBSD.ORG Thu Jun 11 06:24:51 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DDDF2106566C; Thu, 11 Jun 2009 06:24:50 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.29]) by mx1.freebsd.org (Postfix) with ESMTP id 68AE28FC23; Thu, 11 Jun 2009 06:24:50 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so731002ywe.13 for ; Wed, 10 Jun 2009 23:24:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=zeAIHuyJO75NmTQdmb0Wh13XbdAQtLY7Zo/1FQcMKtA=; b=SQ+AbTplf+9Rn/XUuFyBtD4ElmkeFbryLM8CVM7IUD9gW8+/aF1oMSdv0D4ajcXMgT HdipY0q5hXjeIjSrEoGb6NoM3hYVkqEdQaG9oLuRPgGI7Aoz5jP0wIxHun0AjkV3yWE0 mFhEFeBFTeyZINcRA/vLBLLnCmrSNrGYm+BXI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Ec0GQy/bvzkzvjspD10pUfDYKH0vy7ZVPtLym960beeefgLQYazI7z66NtraSVddt8 g9RVOsh9hWMRkXd54FLdODkpEyTNlHCOq9111ERLzUcYgHd7/HWc7fnUAnx0x9zKk1i+ EtKSREVgGyv4+PfAs9tABL3wsnXujJAWHoe+E= MIME-Version: 1.0 Received: by 10.150.229.7 with SMTP id b7mr4376168ybh.255.1244701489699; Wed, 10 Jun 2009 23:24:49 -0700 (PDT) In-Reply-To: References: <7d6fde3d0906101944t7a04ff7ejdd415938d3e1483c@mail.gmail.com> <7d6fde3d0906101950r7640dbf5va8181fd80e2e07ba@mail.gmail.com> Date: Wed, 10 Jun 2009 23:24:49 -0700 Message-ID: <7d6fde3d0906102324i7c296d40pdf5a5e853c359bc3@mail.gmail.com> From: Garrett Cooper To: Dan Naumov Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD-STABLE Mailing List , ata@freebsd.org, pjd@freebsd.org Subject: Re: Issues with gjournal (heaaaaaaaaaaalp!) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jun 2009 06:24:51 -0000 On Wed, Jun 10, 2009 at 10:58 PM, Dan Naumov wrote: > You need to mount your /dev/ad6s1d.journal as /usr and not > /dev/ad6s1d, because this is the new device provided to you by GEOM. > > - Dan Naumov > > > > On Thu, Jun 11, 2009 at 5:50 AM, Garrett Cooper wrote= : >> On Wed, Jun 10, 2009 at 7:44 PM, Garrett Cooper wrot= e: >>> Hi Pawel, ATA, and Stable folks, >>> >>> =A0 =A0This time when I did a reinstall I took the bullet and tried to >>> use gjournaling instead of softupdates. The unfortunate thing is that >>> I can't seem to get it to work. >>> >>> Here's the procedure that I'm trying to follow (based off of [1]): >>> - sysinstall from scratch with a minimal distribution. This creates >>> /usr // /dev/ad6s1d as UFS2 with softupdates disabled. >>> - Pull latest stable sources. Rebuild kernel (with `options >>> GEOM_JOURNAL'), world, install kernel, then world after reboot. >>> - gjournal label -f ad6s1d ad6s2d >>> - mount /dev/ad6s1d /usr # That works (I think...), but prints out the >>> error message below: >>> >>> GEOM_JOURNAL: [flush] Error while writing data (error=3D1) >>> ad6s2d[WRITE(offset=3D512, length=3D6656)] >>> >>> gjournal status says: >>> =A0 =A0 =A0 =A0 =A0 =A0Name =A0 Status =A0 Components >>> ad6s1d.journal =A0 =A0 =A0 N/A =A0 ad6s1d >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= ad6s2d >>> >>> Some issues I noticed: >>> >>> - GJOURNAL ROOT (something) loops infinitely if the device can't be >>> found; this should probably time out and panic / exit if a device >>> becomes unavailable (depends on fstab values in the final 2 fields no >>> doubt). I did this by accident when I forgot to add iir statically to >>> the kernel. >>> - The LiveCD doesn't fully support gjournal (userland's there, kernel >>> support isn't). Kind of annoying and counterproductive... >>> - Existing journal partitions disappeared when I upgraded by accident >>> from 7.2-RELEASE to 8-CURRENT (silly me copied my srcs.sup file from >>> my server with label=3D.). That was weird... >>> - When I use gjournal label with an existing filesystem I _must_ use -f= . >>> >>> Any help with this endeavor would be more than appreciated, as I want >>> to enable this functionality before I move on to installing X11, as >>> nvidia-driver frequently hardlocks the desktop (or has in the past). >>> >>> Thanks, >>> -Garrett >>> >>> [1] http://www.freebsd.org/doc/en_US.ISO8859-1/articles/gjournal-deskto= p/article.html >> >> And to answer another potential question, I've tried mounting both >> with -o rw,async and with -o rw. >> Thanks! >> -Garrett Hi Dan, I'm doing that right now =3D\... orangebox# mount /dev/ad6s1a on / (ufs, local) devfs on /dev (devfs, local) /dev/ad6s1d.journal on /usr (ufs, asynchronous, local) /dev/ad6s1e on /usr/home (ufs, local) /dev/ad6s1f on /var (ufs, local) Thanks! -Garrett