From: Emmanuel Florac <eflorac@intellique.com>
To: David Chinner <dgc@sgi.com>, xfs@oss.sgi.com
Subject: Re: XFS crash on linux raid
Date: Fri, 4 May 2007 09:06:13 +0200 [thread overview]
Message-ID: <20070504090613.7c0f97d3@galadriel.home> (raw)
In-Reply-To: <20070504005922.GC32602149@melbourne.sgi.com>
Le Fri, 4 May 2007 10:59:22 +1000 vous écriviez:
> Where there any I/o errors reported before the shutdown?
>
Nope. To make it clear : the problem can be reproduce on several
different systems, different motherboards, different drives, different
RAID controllers... This isn't a hardware problem.
> > On a similar hardware with 2 3Ware-9550 16x750GB striped together,
> > but running 2.6.17.13, I had a similar fs crash last week.
> > Unfortunately I don't have the logs at hand, but we where able to
> > reproduce several times the crash at home :
>
> Hmm - 750GB drives are brand new. i wouldn't rule out media issues
> at this point...
The problem is quite easily reproduced with 500GB drives too.
> > Filesystem "md0": XFS internal error xfs_btree_check_sblock at line
> > 336 of file fs/xfs/xfs_btree.c. Caller 0xc01fb282 <c0214568>
>
> Memory corruption?
Tried with different RAMs, and the problem occurs on ECC RAM too.
> >
> > Out of curiosity, I've tried to use reiserfs (just to see how it
> > compares regarding this). Reiserfs crashed before even writing
> > 100MB!
>
> That indicates there's something wrong other than the filesystem.
> I'd suggest making sure your raid arrays, memory, etc are all
> functioning correctly first.
They are. I've tested 5 different machines so far (Supermicro or Tyan
mobos, kingston RAM, Intel or AMD cpus, hitachi and seagate drives...)
> What platform are you running on? Are you running ia32 with 4k stacks?
Yes. I'll try this week 2.6.18.8 thoroughly and 2.6.20.11 too. Then
jfs, just to be sure.
--
--------------------------------------------------
Emmanuel Florac www.intellique.com
--------------------------------------------------
next prev parent reply other threads:[~2007-05-04 7:29 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-03 14:45 XFS crash on linux raid Emmanuel Florac
2007-05-03 23:02 ` Chris Wedgwood
2007-05-04 0:59 ` David Chinner
2007-05-04 7:06 ` Emmanuel Florac [this message]
2007-05-04 7:33 ` David Chinner
2007-05-04 13:25 ` Emmanuel Florac
2007-05-04 14:55 ` Eric Sandeen
2007-05-04 15:30 ` Emmanuel Florac
2007-05-04 23:20 ` Chris Wedgwood
2007-05-05 15:19 ` Emmanuel Florac
2007-05-05 16:50 ` Eric Sandeen
2007-05-05 20:35 ` Chris Wedgwood
2007-05-05 20:58 ` Emmanuel Florac
2007-05-05 22:12 ` Chris Wedgwood
2007-05-06 17:21 ` Emmanuel Florac
2007-05-05 20:57 ` Emmanuel Florac
2007-11-19 18:10 ` Alexander Bergolth
2007-11-19 23:44 ` Chris Wedgwood
2007-11-21 15:39 ` Alexander 'Leo' Bergolth
2007-05-04 15:58 ` Martin Steigerwald
2007-05-04 21:43 ` Emmanuel Florac
2007-05-05 4:49 ` Eric Sandeen
2007-05-05 15:18 ` Emmanuel Florac
2007-05-05 16:47 ` Eric Sandeen
2007-05-05 20:56 ` Emmanuel Florac
[not found] ` <20070505210002.GC17112@tuatara.stupidest.org>
2007-05-06 17:21 ` Emmanuel Florac
2007-05-06 17:26 ` Chris Wedgwood
2007-05-06 18:36 ` Emmanuel Florac
2007-05-05 20:56 ` Chris Wedgwood
2007-05-06 17:19 ` Emmanuel Florac
2007-05-06 17:56 ` Martin Steigerwald
2007-05-07 2:11 ` David Chinner
2007-05-07 10:07 ` Emmanuel Florac
2007-07-30 4:07 ` richid
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=20070504090613.7c0f97d3@galadriel.home \
--to=eflorac@intellique.com \
--cc=dgc@sgi.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