From: Dave Chinner <david@fromorbit.com>
To: Federico Sevilla III <jijo@fs3.ph>
Cc: 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 09:46:36 +1100 [thread overview]
Message-ID: <20090224224636.GF26138@disturbed> (raw)
In-Reply-To: <1235480661.17293.28.camel@disciplina.fs3.ph>
[please don't reply to year old message threads with a new problem]
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?
....
> On one of the servers now, on the same file system that had trouble, we
> are having the following messages (the system otherwise remains usable,
> though, which is weird):
>
> 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.
> 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.
> Please help me understand what the cause of this problem could be.
Could be anything. Knowing what caused you systems to crash in the
first place would be handy....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-02-24 22:47 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 [this message]
2009-02-25 10:00 ` Federico Sevilla III
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=20090224224636.GF26138@disturbed \
--to=david@fromorbit.com \
--cc=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