On Fri, Aug 25, 2006 at 09:22:26PM -0500, Eric Anderson wrote: > I got this error today, while some very heavy disk access was occurring: > > > Aug 25 13:47:07 snapshot1 kernel: fsync: giving up on dirty > Aug 25 13:47:07 snapshot1 kernel: 0xffffff01bbb99a20: tag devfs, type VCHR > Aug 25 13:47:07 snapshot1 kernel: usecount 1, writecount 0, refcount 445 > mountedhere 0xffffff023ee20800 > Aug 25 13:47:07 snapshot1 kernel: flags () > Aug 25 13:47:07 snapshot1 kernel: v_object 0xffffff01c34afb60 ref 0 pages > 16386 > Aug 25 13:47:07 snapshot1 kernel: lock type devfs: EXCL (count 1) by thread > 0xffffff023f11d980 (pid 46)#0 0xffffffff803eeaa6 at lockmgr+0x5f6 > Aug 25 13:47:07 snapshot1 kernel: #1 0xffffffff8065e8d1 at VOP_LOCK_APV+0x81 > Aug 25 13:47:07 snapshot1 kernel: #2 0xffffffff8047015b at vn_lock+0x6b > Aug 25 13:47:07 snapshot1 kernel: #3 0xffffffff805719be at ffs_sync+0x1fe > Aug 25 13:47:07 snapshot1 kernel: #4 0xffffffff80472045 at > vfs_write_suspend+0x95 > Aug 25 13:47:07 snapshot1 kernel: #5 0xffffffff80b794a5 at > g_journal_switcher+0xa55 > Aug 25 13:47:07 snapshot1 kernel: #6 0xffffffff803e3cdb at fork_exit+0xbb > Aug 25 13:47:07 snapshot1 kernel: #7 0xffffffff805f39ce at fork_trampoline+0xe > Aug 25 13:47:07 snapshot1 kernel: > Aug 25 13:47:07 snapshot1 kernel: dev label/vol11-data.journal > Aug 25 13:47:07 snapshot1 kernel: GEOM_JOURNAL: Cannot suspend file system > /vol11 (error=35).
I'm aware of this, but it is harmless. On journal switch gjournal cannot synchronize the file system, so it will try again later. It should be probably better logged (as a warning). -- Pawel Jakub Dawidek http://www.wheel.pl [EMAIL PROTECTED] http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am!
pgpjKHQzQnVJy.pgp
Description: PGP signature
