public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Federico Sevilla III <jijo@fs3.ph>
To: Linux XFS <linux-xfs@oss.sgi.com>
Subject: Re: xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c
Date: Wed, 25 Feb 2009 18:00:51 +0800	[thread overview]
Message-ID: <1235556051.17569.4.camel@disciplina.fs3.ph> (raw)
In-Reply-To: <20090224224636.GF26138@disturbed>


[-- Attachment #1.1: Type: text/plain, Size: 1898 bytes --]

On Wed, 2009-02-25 at 09:46 +1100, Dave Chinner wrote:
> On Tue, Feb 24, 2009 at 09:04:21PM +0800, Federico Sevilla III wrote:
> > Hi,
> > 
> > Recently, we had two file servers crash during periods of increased load
> > (increased access from workstations in the LAN). After the crash, the
> > XFS file systems would no longer mount. The mount process would just
> > stay in state D, with no progress, and no significant disk activity.
> 
> What was the cause of the crash?

The engineers on site were unable to copy the exact error message, but
whatever could be read of a photograph of the screen seems to point to
similar issues with xfs_trans_read_buf error 5 as we're beginning to see
now.

We are unsure of the cause of the crash but know that the system load
was higher than usual because of some larger files that people were busy
working on at the time.

> >         attempt to access beyond end of device
> >         sda7: rw=0, want=154858897362229008, limit=3885978852
> >         I/O error in filesystem ("sda7") meta-data dev sda7 block 0x2262b58bf959708       ("xfs_trans_read_buf") error 5 buf count 4096
> 
> A corrupted extent pointer of some kind. xfs_repair should have
> found this. Can you run xfs_repair again? If it doesn't find
> anything, please upgrade xfs_repair to the latest version and
> try again.

Will do, and will revert to the list again with the results.

> > Both servers use CentOS5 with the Linux 2.6.18-92.1.22.el5 kernel. For
> 
> Oh. XFS is not really supported on that platform because it is pretty much
> completely untested on RHEL based kernels.

What would be the "community endorsed" approach to using our favorite
file system on CentOS 5? Would you recommend we go with the CentOSPlus
kernels instead?

Thank you very much.

Cheers!

-- 
Federico Sevilla III
F S 3 Consulting Inc.
http://www.fs3.ph

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-02-25 10:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-24 13:04 xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c Federico Sevilla III
2009-02-24 22:46 ` Dave Chinner
2009-02-25 10:00   ` Federico Sevilla III [this message]
2009-02-25 11:51     ` Michael Monnerie
2009-02-25 18:47     ` Federico Sevilla III
     [not found] <B3EDBE0F860AF74BAA82EF17A7CDEDC660BE05A3@svits26.main.ad.rit.edu>
2007-12-21  2:01 ` Jay Sullivan
2008-01-03 15:55   ` Jay Sullivan
2008-08-04 16:55   ` Richard Freeman
  -- strict thread matches above, loose matches on Subject: below --
2007-11-02  2:08 Jay Sullivan
2007-11-02  5:18 ` David Chinner
2007-11-01 20:06 Jay Sullivan
2007-11-02  2:14 ` Eric Sandeen
2007-11-02  2:22   ` Jay Sullivan
2007-11-02  2:30     ` Eric Sandeen
2007-11-02  9:07       ` Ralf Gross
2007-11-02 16:10         ` Eric Sandeen
2007-11-02 14:00       ` Jay Sullivan
2007-11-02 14:49         ` Jay Sullivan
2007-11-14 15:05           ` Jay Sullivan
2007-11-15  3:26             ` Eric Sandeen
2007-11-02  4:37   ` Timothy Shimmin

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=1235556051.17569.4.camel@disciplina.fs3.ph \
    --to=jijo@fs3.ph \
    --cc=linux-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