From: Nathan Scott <nathans@sgi.com>
To: Avuton Olrich <avuton@gmail.com>
Cc: linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: XFS crashed twice, once in 2.6.16.20, next in 2.6.17, reproducable
Date: Tue, 20 Jun 2006 16:43:38 +1000 [thread overview]
Message-ID: <20060620164338.A1080488@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <3aa654a40606192338v751150fp5645d1d2943316ea@mail.gmail.com>; from avuton@gmail.com on Mon, Jun 19, 2006 at 11:38:58PM -0700
On Mon, Jun 19, 2006 at 11:38:58PM -0700, Avuton Olrich wrote:
> On 6/19/06, Nathan Scott <nathans@sgi.com> wrote:
> > If so, can you try Mandy's patch below, to see if it is addressing
> > the root cause of your problem? If problems persist, a reproducible
> > test case would be wonderful, if one can be found..
>
> I'm sorry, the patch doesn't change anything. It never makes it though
> the xfs_repair due to the above error. If there's any information I
> can get for you please let me know.
Oh - thats a kernel patch, not a repair patch, I was more interested
in whether the initial corruption could be reproduced. Which version
of xfs_repair are you running? (xfs_repair -V) xfsprogs-2.7.18 will
resolve your problem, I suspect.
cheers.
--
Nathan
next prev parent reply other threads:[~2006-06-20 6:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 7:44 Avuton Olrich
2006-06-19 10:35 ` daniel+devel.linux.lkml
2006-06-20 6:10 ` Nathan Scott
2006-06-20 6:38 ` Avuton Olrich
2006-06-20 6:43 ` Nathan Scott [this message]
2006-06-20 6:50 ` Avuton Olrich
2006-06-20 6:52 ` Nathan Scott
2006-06-20 8:20 ` Avuton Olrich
2006-06-20 8:39 ` Duncan Sands
2006-06-22 2:56 ` Nathan Scott
2006-06-25 10:09 ` Duncan Sands
2006-06-25 13:55 ` Duncan Sands
2006-06-20 6:40 ` Avuton Olrich
2006-06-20 8:57 ` Justin Piszcz
2006-06-20 17:01 ` Avuton Olrich
2006-06-20 17:15 ` Justin Piszcz
2006-06-20 17:21 ` Avuton Olrich
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=20060620164338.A1080488@wobbly.melbourne.sgi.com \
--to=nathans@sgi.com \
--cc=avuton@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®