https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #23 from Steve Wills ---
r324941
https://svnweb.freebsd.org/base?view=revision=324941
did adjust the default value of vfs.aio.max_aio_queue, but I'm not sure if
that's sufficient. Seems to me what's needed is either:
*
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #15 from rozhuk...@gmail.com ---
Time to close this?
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-virtualization@freebsd.org mailing list
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #16 from p...@twisted.org.uk ---
(In reply to rozhuk.im from comment #15)
Yes, I would says so, this has been stable for me now for many years with the
AIO tunings above. I run several machines on virtuabox on zvols fine.
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #17 from VVD ---
(In reply to pete from comment #16)
> Yes, I would says so, this has been stable for me now for many years with the
> AIO tunings above. I run several machines on virtuabox on zvols fine.
Same here too. But
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
Bernhard Froehlich changed:
What|Removed |Added
Status|In Progress |Closed
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #20 from rozhuk...@gmail.com ---
(In reply to Kurt Jaeger from comment #19)
1. It works.
2. No one wants dig in to it in past 2-3 years.
I suspect that there is some internal IO queue, probably with limit, and
default limit in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #21 from Anton Saietskii ---
(In reply to rozhuk.im from comment #20)
"Overcome By Events" as closure code fits much better, although not perfect
also.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #19 from Kurt Jaeger ---
It's a bit strange to close a bug report with "works as intended" with a sysctl
tuning fix, and not trying to find the root cause.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #22 from Kurt Jaeger ---
It's not even overcome by events. The problem is probably still there, the
sysctl fix only masks it.
--
You are receiving this mail because:
You are the assignee for the bug.
