From: Sagar Borikar <sagar_borikar@pmc-sierra.com>
To: Sagar Borikar <sagar_borikar@pmc-sierra.com>, xfs@oss.sgi.com
Subject: Re: Xfs Access to block zero exception and system crash
Date: Wed, 02 Jul 2008 11:05:41 +0530 [thread overview]
Message-ID: <486B13AD.2010500@pmc-sierra.com> (raw)
In-Reply-To: <20080702051337.GX29319@disturbed>
Dave Chinner wrote:
> On Wed, Jul 02, 2008 at 09:48:46AM +0530, Sagar Borikar wrote:
>
>> Dave Chinner wrote:
>>
>>> On Mon, Jun 30, 2008 at 03:54:44PM +0530, Sagar Borikar wrote:
>>> Sure - just like any other workload that generates enough
>>> extents. Like I said originally, we've fixed so many problems
>>> in this code since 2.6.18 I'd suggest that your only sane
>>> hope for us to help you track done the problem is to upgrade
>>> to a current kernel and go from there....
>>>
>>>
>> Thanks again Dave. But we can't upgrade the kernel as it is already in
>> production and on field.
>>
>
> Yes, but you can run it in your test environment where you are
> reproducing this problem, right?
>
>
Unfortunately the architecture is customized mips for which the standard
kernel port is
not available and we have to port the new kernel in order to try this
which is why I was
hesitating to do this.
>> So do you think, periodic cleaning of file system using xfs_fsr can
>> solve the issue?
>>
>
> No, at best it would only delay the problem (whatever it is).
>
>
>> If not, could you
>> kindly direct me what all patches were fixing similar problem? I can try
>> back porting them.
>>
>
> I don't have time to try to identify some set of changes from the
> past 3-4 years that might fix your problem. There may not even be a
> patch that fixes your problem, which is one of the reasons why I've
> asked if you can reproduce it on a current kernel....
>
> I pointed you the files that the bug could lie in earlier in the
> thread. You can find the history of changes to those files via the
> mainline git repository or via the XFS CVS repository. You'd
> probably do best to look at the git tree because all the changes are
> well described in the commit logs and you should be able to isolate
> ones that fix btree problems fairly easily...
>
> Cheers,
>
> Dave.
>
Sure I'll go through these changelogs. Thanks for all your help and
really appreciate your
time. I hope you don't mind to help me in future if I find something new :)
Regards,
Sagar
next prev parent reply other threads:[~2008-07-02 5:34 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 [this message]
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
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=486B13AD.2010500@pmc-sierra.com \
--to=sagar_borikar@pmc-sierra.com \
--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