From: Cedric - Equinoxe Media <cedric@e-m.fr>
To: David Chinner <dgc@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs crash
Date: Wed, 7 Nov 2007 11:58:14 +0100 [thread overview]
Message-ID: <20071107105814.GD25295@e-m.fr> (raw)
In-Reply-To: <20071106205556.GZ995458@sgi.com>
On 07/11/2007 07:55, David Chinner wrote:
> On Tue, Nov 06, 2007 at 05:07:21PM +0100, Cedric - Equinoxe Media wrote:
> > I just had exactly the same crash again today :
> > /dev/sda4 on /filer type xfs (rw,noexec,nosuid,nodev,noatime)
>
> What did xfs_check tell you about the corruption?
I had quite the same message as last time, forgot to copy/paste...
> > Seems to be again on a setattr() ?
>
> Doing a truncation freeing some blocks.
>
> What is the client doing (i.e. io patterns, application, etc) to
> cause this? can you reproduce it without NFS being used? To track
> this down I'm going to need a reproducable test case....
It is 5 web servers with php as nfsv3 clients.
> Seeing this is a brand new server, have you run and soak or stress
> test on the raw storage to confirm it is error free?
I have run bonnie++ and memtest86+ with no errors.
I am now trying to recompile linux without nfsv4, ACL and all
experimental features of nfs and xfs.
--
Cédric Tabary
Ingénieur réseau - Equinoxe Media
+33 (0)6 77 45 80 15
next prev parent reply other threads:[~2007-11-07 10:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 21:51 xfs crash Cedric - Equinoxe Media
[not found] ` <20071106082632.GU995458@sgi.com>
2007-11-06 9:21 ` Cedric - Equinoxe Media
2007-11-06 16:07 ` Cedric - Equinoxe Media
2007-11-06 16:44 ` Justin Piszcz
2007-11-06 17:08 ` Cedric - Equinoxe Media
2007-11-06 20:55 ` David Chinner
2007-11-07 10:58 ` Cedric - Equinoxe Media [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-05-18 4:45 Jabir M
2010-05-18 6:02 ` Dave Chinner
2010-05-19 11:26 ` Jabir M
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=20071107105814.GD25295@e-m.fr \
--to=cedric@e-m.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.