gjournal error?

[Pawel Jakub Dawidek]

On Tue, Mar 20, 2007 at 11:51:03PM +0100, Kay Abendroth wrote:
> today I got this in my /var/log/messages:
> 
> Mar 20 13:42:45 halo kernel: fsync: giving up on dirty
> Mar 20 13:42:45 halo kernel: 0xc5eef440: tag devfs, type VCHR
> Mar 20 13:42:45 halo kernel: usecount 1, writecount 0, refcount 194
> mountedhere 0xc5e2d500
> Mar 20 13:42:45 halo kernel: flags ()
> Mar 20 13:42:45 halo kernel: v_object 0xc14316b4 ref 0 pages 4628
> Mar 20 13:42:45 halo kernel: lock type devfs: EXCL (count 1) by thread
> 0xc5b2f900 (pid 33)
> Mar 20 13:42:45 halo kernel: dev ad0s1f.journal
> Mar 20 13:42:45 halo kernel: GEOM_JOURNAL: Cannot suspend file system
> /usr (error=35).
> 
> System was running all the time and I didn't try to umount /usr. Can I
> ignore that? OS version is 6.2-STABLE with gjournal patch. Only my /usr
> is gjournaled and I didn't had any problems with it so far.

Yes, it's harmless.

-- 
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/20070321/8967202b/attachment.pgp