Eric Sandeen wrote:
Sagar Borikar wrote:
Ok. So initially our multi client iozone stress test used to fail.
Are these multiple nfs clients?
Actually mix of them. 15 CIFS clients, 4 NFS clients ( 19 iozone clients
) , 2 FTP clients,
4 HTTP transfers. ( Total 25 transactions simultaneously )
But
as it took 2-3 days
to replicate the issue, I tried the test, standalone on MIPS and
the iozone test again?
iozone test is continuously giving the access to block zero exception
and xfs shutdown
errors with transaction cancel exceptions plus alloc btree corruption
exception which I
reported earlier. And my test gives transaction cancel exception and
block zero exception
with processes under test in deadlock state on MIPS but on x86 there are
no exceptions but
only incomplete copies due to uninterruptible sleep state and deadlock.
observed similar failures which
I used to get in multi client test. The test is exactly same what I do
in mutli client
iozoen over network. Hence I came to conclusion that if we fix system to
pass my test case
then we can try iozone test with that fix. And now on x86 with 2.6.24,
I am finding similar deadlock but
the system is responsive and there are no lockups or exceptions. Do you
observe similar failures on x86
at your setup?
So far I've not seen the deadlocks.
Could you kindly try with my test? I presume you should see failure
soon. I tried this on
2 different x86 systems 2 times ( after rebooting the system ) and I saw
it every time.
Also do you think the issues which I am seeing on x86 and
MIPS are coming from the
same sources?
hard to say at this point, I think.
-Eric
Thanks
Sagar
|