On Fri, Dec 28, 2012 at 01:27:24PM +0200, Konstantin Belousov wrote:
Please try the following patch. It is against HEAD, might need some
adjustments for 8. I do the resume and write accounting atomically,
not allowing other suspension to intervent between.
So is this only limited to snapshot
Konstantin Belousov wrote:
On Thu, Dec 27, 2012 at 12:28:54PM +0100, Andreas Longwitz wrote:
db alltrace (pid 18 and 7126)
Tracing command g_journal switcher pid 18 tid 100076 td 0xff0002bd5000
sched_switch() at sched_switch+0xde
mi_switch() at mi_switch+0x186
sleepq_wait() at
On Fri, Dec 28, 2012 at 10:19:31AM +0100, Andreas Longwitz wrote:
Konstantin Belousov wrote:
On Thu, Dec 27, 2012 at 12:28:54PM +0100, Andreas Longwitz wrote:
db alltrace (pid 18 and 7126)
Tracing command g_journal switcher pid 18 tid 100076 td 0xff0002bd5000
sched_switch() at
Konstantin Belousov wrote:
Please try the following patch. It is against HEAD, might need some
adjustments for 8. I do the resume and write accounting atomically,
not allowing other suspension to intervent between.
diff --git a/sys/kern/vfs_vnops.c b/sys/kern/vfs_vnops.c
index
On Thu, Dec 27, 2012 at 12:28:54PM +0100, Andreas Longwitz wrote:
On a FreeBSD 8-Stable machine with UFS + GJOURNAL (no SU) I observed the
same behaviour as described for UFS+SU+J in
lists.freebsd.org/pipermail/freebsd-current/2012-January/030937.html.
The snapshot was initiated by amanda
Konstantin Belousov wrote:
On Thu, Dec 27, 2012 at 12:28:54PM +0100, Andreas Longwitz wrote:
On a FreeBSD 8-Stable machine with UFS + GJOURNAL (no SU) I observed the
same behaviour as described for UFS+SU+J in
lists.freebsd.org/pipermail/freebsd-current/2012-January/030937.html.
The
On Thu, Dec 27, 2012 at 06:47:05PM +0100, Andreas Longwitz wrote:
Konstantin Belousov wrote:
On Thu, Dec 27, 2012 at 12:28:54PM +0100, Andreas Longwitz wrote:
On a FreeBSD 8-Stable machine with UFS + GJOURNAL (no SU) I observed the
same behaviour as described for UFS+SU+J in