From: David Chinner <dgc@sgi.com>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: David Chinner <dgc@sgi.com>, xfs@oss.sgi.com
Subject: Re: XFS crash on linux raid
Date: Mon, 7 May 2007 12:11:22 +1000 [thread overview]
Message-ID: <20070507021122.GQ32602149@melbourne.sgi.com> (raw)
In-Reply-To: <20070504152546.614374ac@harpe.intellique.com>
On Fri, May 04, 2007 at 03:25:46PM +0200, Emmanuel Florac wrote:
> Le Fri, 4 May 2007 17:33:44 +1000
> David Chinner <dgc@sgi.com> écrivait:
>
> > Well, there's your problem. Stack overflows. IMO, if you use a
> > filesystem, you shouldn't use 4k stacks. ;)
> >
> > If you remake you kernel with 8k stacks then your problems will
> > most likely go away.
>
> Well, I've double-checked the asm-i386/module.h, and it actually looks
> like 4K stacks is NOT the default, so I must be using 8K, isn't it?
Yes.
> I've ran the same test on the same machine but WITHOUT software raid-0
> (so write barriers are in use), and all went well, more than 3TB
> written without a glitch. I still think there's something related to
> the write barriers here. I'll try with another RAID controller, Adaptec
> for instance, to get sure the 3ware driver isn't involved. I'll also try
> again with an amd64 kernel.
So you use software raid and you get corruptions, right? I doubt this has
anything to do with write barriers - if it does thats an indication
of broken drivers or hardware.....
Can you run with "-o nobarrier" and no software raid and see if you
still have a problem?
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2007-05-07 2:11 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
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 [this message]
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=20070507021122.GQ32602149@melbourne.sgi.com \
--to=dgc@sgi.com \
--cc=eflorac@intellique.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