kern/133604: [panic] writing to gjournal on a gvinum volume

Peter Much pmc at
Sat Apr 11 07:20:05 PDT 2009

>Number:         133604
>Category:       kern
>Synopsis:       [panic] writing to gjournal on a gvinum volume
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Sat Apr 11 14:20:03 UTC 2009
>Originator:     Peter Much
>Release:        FreeBSD 7.2-PRERELEASE i386
System: FreeBSD 7.2-PRERELEASE FreeBSD 7.2-PRERELEASE #1: Thu Apr 9 22:23:20 CEST 2009 root at i386


A gjournal can be created on a vinum volume. But when writing the 
filesystem onto it, 2-3 seconds later the system always does crash. 
The panic comes from the gv_v worker process, interrupt-called.

I am managing all my filesystems with gvinum (it seems the best 
approach to a volume manager that we currently have), so I need
the other GEOM goodies (like crypt, compress, whatever) *above*
a vinum volume.
When I tried last (on RELEASE 5), there seemed to be no way at all
to achieve such.
Now it looks quite good - gbde and geli seem to work fine, their 
products can even be brought back into vinum as a "new" drive, so
to slice various filesystems from them.

Sadly, journaling is the only thing I really need from RELEASE 7,
and I only need it for about one filesystem, for the database of
my tapebackup-server (to overcome the "full_page_writes" need in 
postgresql and get smaller redo-logs).

But I am not sure if coupling gvinum with other GEOM tools is 
indeed an intended functionality ; therefore I pronounce this as 
a change-request ;)


 - create some simple concat volume 'myjfs' in gvinum 
 - gjournal load
 - gjournal label -chs 100m gvinum/myjfs
 - newfs -J /dev/gvinum/myjfs.journal


When exporting the gvinum volume with ggated to localhost, then bringing 
it in again with ggatec, and creating the journal on ggate0, the
panic does not happen. But this performs rather bad and occasionally
hangs completely - maybe needs careful buffer tuning.
I'm trying ZFS now - which seems to run fine above gvinum - and
would even be a nice replacement for gvinum in toto - but I dowbt this 
will run on that tapebackup-server without installing a lot more ram
(there is only 256MB).

More information about the freebsd-bugs mailing list