Journaling UFS with gjournal.

Pawel Jakub Dawidek pjd at FreeBSD.org
Fri Jun 23 19:23:07 UTC 2006


On Thu, Jun 22, 2006 at 05:00:03PM +0200, Oliver Fromme wrote:
+> Pawel Jakub Dawidek <pjd at freebsd.org> wrote:
+>  > GJournal was designed to journal GEOM providers, so it actually works
+>  > below file system layer, but it has hooks which allow to work with
+>  > file systems. In other words, gjournal is not file system-depended,
+>  > it can work probably with any file system with minimum knowledge
+>  > about it. I implemented only UFS support.
+> 
+> Very cool.  Thanks for providing journaling to FreeBSD.
+> 
+> How "stable" should your code be considered?  I assume it
+> hasn't been subject to testing by a wider audience yet,
+> so it should be considered "alpha" quality, right?

It works currently on about 100 heavy loaded servers in production and
it works well. There is still one issue I'm trying to track down, but it
is very hard to trigger. It doesn't currupt the data, but can hang the
system.

But. GJournal was tested only on a specific workload, so it should be
considered experimental!

+> First of all, is it possible to add journaling to an
+> existing file system, i.e. without having to dump, newfs
+> and restore?

If you have an additional partition for journal you may try, but
gjournal will steal the last sector from the provider holding your file
system. I can't tell you it is safe or not.

+>  > When last
+>  > name is deleted, the file/directory is moved to the .deleted/
+>  > directory and removed from there on last close.
+> 
+> Is that directory located in the root of the file system,
+> similar to the .snap directory for snapshots?

Yes.

+>  > [...]
+>  > Reading. grep -r on two src/ directories in parallel:
+>  > UFS:            84s
+>  > UFS+SU:         138s
+>  > gjournal(1):    102s
+>  > gjournal(2):    89s
+>  > 
+>  > As you can see, even on one disk, untaring eight src.tgz is two times
+>  > faster than UFS+SU. I've no idea why gjournal is faster in reading.
+> 
+> Maybe it is because of the atime updates.  You'll get a lot
+> of them when grepping recursively on the src tree.

AFAIR file system was mounted with noatime, but I'm not sure.

-- 
Pawel Jakub Dawidek                       http://www.wheel.pl
pjd at FreeBSD.org                           http://www.FreeBSD.org
FreeBSD committer                         Am I Evil? Yes, I Am!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20060623/3b5d66bb/attachment.pgp


More information about the freebsd-fs mailing list