Issues with gjournal (heaaaaaaaaaaalp!)
yanefbsd at gmail.com
Thu Jun 11 06:24:51 UTC 2009
On Wed, Jun 10, 2009 at 10:58 PM, Dan Naumov<dan.naumov at gmail.com> 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<yanefbsd at gmail.com> wrote:
>> On Wed, Jun 10, 2009 at 7:44 PM, Garrett Cooper<yanefbsd at gmail.com> wrote:
>>> Hi Pawel, ATA, and Stable folks,
>>> This 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 ):
>>> - 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=1)
>>> ad6s2d[WRITE(offset=512, length=6656)]
>>> gjournal status says:
>>> Name Status Components
>>> ad6s1d.journal N/A ad6s1d
>>> 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=.). 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).
>>>  http://www.freebsd.org/doc/en_US.ISO8859-1/articles/gjournal-desktop/article.html
>> And to answer another potential question, I've tried mounting both
>> with -o rw,async and with -o rw.
I'm doing that right now =\...
/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)
More information about the freebsd-stable