linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Patrick Ale" <patrick.ale@gmail.com>
To: "Ramy M. Hassan" <ramy@gawab.com>
Cc: linux-kernel@vger.kernel.org, "Ahmed El Zein" <a.elzein@gawab.net>
Subject: Re: xfs internal error on a new filesystem
Date: Wed, 14 Feb 2007 11:48:45 +0100	[thread overview]
Message-ID: <8d158e1f0702140248h63d99e3hdf4ccc155f5fdef6@mail.gmail.com> (raw)
In-Reply-To: <20070214102432.6346.qmail@info6.gawab.com>

On 2/14/07, Ramy M. Hassan <ramy@gawab.com> wrote:
> Hello,
> We got the following xfs internal error on one of our production servers:

Hi, I want firstly to make a disclaimer that I am not an XFS or kernel
guru, what I am writing now is purely my experience, since I use XFS
on all my machines, on different disks and all.


I encountered the problem you have now, twice over the past three years.
Once it was caused by a faulty disk where the 8MB cache on the disk
was faulty, causing corruption, and one time it was cause of, what
seems to be, a CPU that couldnt handle XFS. This sounds illogical, and
to me too, honestly, but the explanation I got was that XFS writes are
quite CPU intensive, especialy when you write with 500MB/s and we
tried to do this on a PII-400Mhz.

I tried reiserfs aswell, and I honestly cant give you one reason to
switch back to it. I love XFS, always did, its fast and reliable.
Problems that I had were never related to XFS but to hardware that had
to deal with XFS in a way (CPU/disk).

And, xfs_repair DID repair my filesystems, the data was on the disks,
and valid, XFS just shut down my filesystem cause it found my journal
not reliable/corrupted.

Again, please be aware that I am just a regular user who likes to play
around with linux and the kernel, I am no expert in the field of XFS
or its relations.


I hope this helps you a bit.


Patrick

  parent reply	other threads:[~2007-02-14 10:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-14 10:24 xfs internal error on a new filesystem Ramy M. Hassan 
2007-02-14 10:40 ` Jan-Benedict Glaw
2007-02-14 10:48 ` Patrick Ale [this message]
2007-02-15  9:16 ` David Chinner
2007-02-15 16:19 Ahmed El Zein
2007-02-16 17:58 ` David Chinner
2007-02-18 13:56 ` Leon Kolchinsky

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=8d158e1f0702140248h63d99e3hdf4ccc155f5fdef6@mail.gmail.com \
    --to=patrick.ale@gmail.com \
    --cc=a.elzein@gawab.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ramy@gawab.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;
as well as URLs for NNTP newsgroup(s).