From: Sagar Borikar <sagar_borikar@pmc-sierra.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Dave Chinner <david@fromorbit.com>,
Nathan Scott <nscott@aconex.com>,
xfs@oss.sgi.com
Subject: Re: Xfs Access to block zero exception and system crash
Date: Mon, 07 Jul 2008 09:28:53 +0530 [thread overview]
Message-ID: <4871947D.2090701@pmc-sierra.com> (raw)
In-Reply-To: <487191C2.6090803@sandeen.net>
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
>>
>>
>
>
next prev parent reply other threads:[~2008-07-07 3:57 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-24 7:03 Xfs Access to block zero exception and system crash Sagar Borikar
2008-06-25 6:48 ` Sagar Borikar
2008-06-25 8:49 ` Dave Chinner
2008-06-26 6:46 ` Sagar Borikar
2008-06-26 7:02 ` Dave Chinner
2008-06-27 10:13 ` Sagar Borikar
2008-06-27 10:25 ` Sagar Borikar
2008-06-28 0:05 ` Dave Chinner
2008-06-28 16:47 ` Sagar Borikar
2008-06-29 21:56 ` Dave Chinner
2008-06-30 3:37 ` Sagar Borikar
[not found] ` <20080630034112.055CF18904C4@bby1mta01.pmc-sierra.bc.ca>
2008-06-30 6:07 ` Sagar Borikar
2008-06-30 10:24 ` Sagar Borikar
2008-07-01 6:44 ` Dave Chinner
2008-07-02 4:18 ` Sagar Borikar
2008-07-02 5:13 ` Dave Chinner
2008-07-02 5:35 ` Sagar Borikar
2008-07-02 6:13 ` Nathan Scott
2008-07-02 6:56 ` Dave Chinner
2008-07-02 11:02 ` Sagar Borikar
2008-07-03 4:03 ` Eric Sandeen
2008-07-03 5:14 ` Sagar Borikar
2008-07-03 15:02 ` Eric Sandeen
2008-07-04 10:18 ` Sagar Borikar
2008-07-04 12:27 ` Dave Chinner
2008-07-04 17:30 ` Sagar Borikar
2008-07-04 17:35 ` Eric Sandeen
2008-07-04 17:51 ` Sagar Borikar
2008-07-05 16:25 ` Eric Sandeen
2008-07-06 17:24 ` Sagar Borikar
2008-07-06 19:07 ` Eric Sandeen
2008-07-07 3:02 ` Sagar Borikar
2008-07-07 3:04 ` Eric Sandeen
2008-07-07 3:07 ` Sagar Borikar
2008-07-07 3:11 ` Eric Sandeen
2008-07-07 3:17 ` Sagar Borikar
2008-07-07 3:22 ` Eric Sandeen
2008-07-07 3:42 ` Sagar Borikar
[not found] ` <487191C2.6090803@sandeen .net>
[not found] ` <4871947D.2090701@pmc-sierr a.com>
2008-07-07 3:47 ` Eric Sandeen
2008-07-07 3:58 ` Sagar Borikar [this message]
2008-07-07 5:19 ` Eric Sandeen
2008-07-07 5:58 ` Sagar Borikar
2008-07-06 4:19 ` Dave Chinner
2008-07-04 15:33 ` Eric Sandeen
2008-06-28 0:02 ` Dave Chinner
[not found] <4872E0BC.6070400@pmc-sierra.com>
[not found] ` <4872E33E.3090107@sandeen.net>
2008-07-08 5:03 ` Sagar Borikar
2008-07-09 16:57 ` Sagar Borikar
2008-07-10 5:12 ` Sagar Borikar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4871947D.2090701@pmc-sierra.com \
--to=sagar_borikar@pmc-sierra.com \
--cc=david@fromorbit.com \
--cc=nscott@aconex.com \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox