search for: vfs_busy

...MNT_IUNLOCK(mp); 1281 if ((error = VFS_SYNC(mp, MNT_SUSPEND)) != 0) (kgdb) p mp->mnt_writeopcount $2 = 1 The deadlock can be explained now: pid 1 (init) sleeps on "mount drain" because mp->mnt_lockref was 1. This setting was done by pid 18 (gjournal switcher) by calling vfs_busy(). pid 18 now sleeps on "suspwt" because mp->mnt_writeopcount was 1. This setting was done by pid 1 before going to sleep by calling vn_start_write() in dounmount(). I think the reason for this deadlock is the commit r249055 which seems not to be compatible with gjournal. Andreas Lo...

...@@ -563,6 +563,9 @@ sync(p, uap) register struct mount *mp, *nmp; int asyncflag; + /* Notify sched_sync() to try flushing syncer_workitem_pending[*] */ + rushjob += syncer_maxdelay; + simple_lock(&mountlist_slock); for (mp = TAILQ_FIRST(&mountlist); mp != NULL; mp = nmp) { if (vfs_busy(mp, LK_NOWAIT, &mountlist_slock, p)) { @@ -2627,6 +2630,10 @@ fsync(p, uap) struct file *fp; vm_object_t obj; int error; + + /* Just return if we are artificially delaying disk syncs */ + if (sync_extdelay) + return (0); if ((error = getvnode(p->p_fd, SCARG(uap, fd), &fp)) !=...

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