search for: vfs_write_suspend

...#3 0xffffffff80407fc6 in _sleep (ident=0xffffff007f7e5364, lock=0xffffff007f7e52f0, priority=<value optimized out>, wmesg=0xffffffff806a0813 "suspwt", timo=0) at /usr/src/sys/kern/kern_synch.c:250 #4 0xffffffff804a25f0 in vfs_write_suspend (mp=0xffffff007f7e52f0) at /usr/src/sys/kern/vfs_vnops.c:1277 #5 0xffffffff80c843bd in g_journal_switcher (arg=<value optimized out>) at /usr/src/sys/modules/geom/geom_journal/../ ../../geom/journal/g_journal.c:2968 #6 0xfffff...

I wouldn't report this if not for one coincidence (which is described below). I have too little facts, so this is more of a mystery problem tale than a real problem report. There are two systems: 1. old, slow, i386, UP, 7-STABLE 2. new, fast, amd64, MP, 6.3-RELEASE Systems are located at different physical locations. What is common between them: 1. they both have the same backup strategy

Hi all, I was intending on trying out gjournal on a new disk i've added in my desktop. I had a look to see what the most recent patch provided by Pawel and found http://people.freebsd.org/~pjd/patches/gjournal6_20061024.patch I created the directories as per Pawel's original post (http://lists.freebsd.org/pipermail/freebsd-fs/2006-June/001962.html) and the patch succeeded with no failed