Thread (1 message) 1 message, 1 author, 2012-08-31
  • (off-list ancestor, not in this archive)
  • RE: Expected Behavior · Jonathan Tripathy <hidden> · 2012-08-31

RE: Expected Behavior

From: Jonathan Tripathy <hidden>
Date: 2012-08-31 12:41:19


On 31.08.2012 13:36, Jonathan Tripathy wrote:
On 31.08.2012 04:47, James Harper wrote:
quoted
quoted
Hi Kent,

I'm going to try and reproduce it myself as well. I just used 
IOMeter in a
Windows DomU with 30 workers, each having an io depth of 256. A 
*very*
heavy workload indeed, but my point was to see if I could break 
something.
Unless the issue is specific to windows causing problems (NTFS or 
whatever),
I'm guessing running fio with 30 jobs and an iodepth of 256 would 
probably
produce a similar load.

BTW, do you have access to a Xen node for testing?
Does the problem resolve itself after you shut down the windows 
DomU?
Or only when you reboot the whole Dom0?
Hi There,

I managed to reproduce this again. I have to reboot the entire Dom0
(the physical server) for it to work properly again.

James, are you able to reproduce this? Kent, are there any other
tests/debug output you need from me?
BTW, I was using IOMeter's 'default' Access Specification with the 
following modifications: 100% random, 66% read, 33% write, and a 2kB 
size. My bcache is formatted for 512bytes.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help