gjournal questions

[Kevin Kramer]

I've already redone the whole thing. here are the steps i took

umount /scr09
umount /scr10
gjournal stop da2.journal
gjournal stop da4.journal

** had not done this on the first attempt
newfs /dev/da1
newfs /dev/da3


gjournal label -v /dev/da2 /dev/da1
gjournal label -v /dev/da4 /dev/da3

newfs -J -L scr09 /dev/da2.journal
newfs -J -L scr10 /dev/da4.journal

mount /scr09
mount /scr10

it is looking much better so far. before, i was getting this in the 
debug (only on /scr10) and my mountd process was always the top process

Sep  1 00:00:11 donkey kernel: fsync: giving up on dirty
Sep  1 00:00:11 donkey kernel: 0xc9ee1bb0: tag devfs, type VCHR
Sep  1 00:00:11 donkey kernel: usecount 1, writecount 0, refcount 198 
mountedher
e 0xc9ebfb00
Sep  1 00:00:11 donkey kernel: flags ()
Sep  1 00:00:11 donkey kernel: v_object 0xc9fbb528 ref 0 pages 5933
Sep  1 00:00:11 donkey kernel: lock type devfs: EXCL (count 1) by thread 
0xc9bd4
180 (pid 38)
Sep  1 00:00:11 donkey kernel: dev ufs/scr10
Sep  1 00:00:11 donkey kernel: GEOM_JOURNAL: Cannot suspend file system 
/scr10 (
error=35).

but now i'm getting clean journal writes, while i'm rsyncing the data 
back. i don't have any real clients yet so i'll enable that after the 
rsync is completed.

Sep  1 10:00:36 donkey kernel: GEOM_JOURNAL[1]: Starting copy of journal.
Sep  1 10:00:36 donkey kernel: GEOM_JOURNAL[1]: Switch time of da4: 
0.002327s
Sep  1 10:00:36 donkey kernel: GEOM_JOURNAL[1]: Entire switch time: 
0.011674s
Sep  1 10:00:36 donkey kernel: GEOM_JOURNAL[1]: Data has been copied.
Sep  1 10:00:46 donkey kernel: GEOM_JOURNAL[1]: Msync time of /scr09: 
0.000008s
Sep  1 10:00:46 donkey kernel: GEOM_JOURNAL[1]: Sync time of /scr09: 
0.000031s
Sep  1 10:00:46 donkey kernel: GEOM_JOURNAL[1]: Suspend time of /scr09: 
0.000094
s
Sep  1 10:00:46 donkey kernel: GEOM_JOURNAL[1]: Starting copy of journal.
Sep  1 10:00:46 donkey kernel: GEOM_JOURNAL[1]: Switch time of da2: 
0.002425s
Sep  1 10:00:46 donkey kernel: GEOM_JOURNAL[1]: Entire switch time: 
0.003477s
Sep  1 10:00:46 donkey kernel: GEOM_JOURNAL[1]: Data has been copied.
Sep  1 10:00:56 donkey kernel: GEOM_JOURNAL[1]: Entire switch time: 
0.000014s
Sep  1 10:01:06 donkey kernel: GEOM_JOURNAL[1]: Entire switch time: 
0.000014s
Sep  1 10:01:16 donkey kernel: GEOM_JOURNAL[1]: Msync time of /scr10: 
0.002388s
Sep  1 10:01:16 donkey kernel: GEOM_JOURNAL[1]: Sync time of /scr10: 
0.002748s
Sep  1 10:01:16 donkey kernel: GEOM_JOURNAL[1]: Suspend time of /scr10: 
0.002751
s




------------------------------

Kevin Kramer
Sr. Systems Administrator
512.418.5725
Centaur Technology, Inc.
www.centtech.com



Pawel Jakub Dawidek wrote the following on 09/01/06 09:59:
> On Fri, Sep 01, 2006 at 08:12:23AM -0500, Kevin Kramer wrote:
>   
>> we left the journaling devices raw. do i need to newfs the journaling device? is eveything else ok besides the newfs of the daX.journal?
>>     
>
> Journal switch times are very long, but this could be caused by SU.
> Could you try to disable SU and turn on gjournal?
> Without "renewfsing" you could do on an unmounted file system:
>
> 	# tunefs -n disable -J enable /dev/daX.journal
>
>