public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: xfs@oss.sgi.com, Ole Tange <tange@binf.ku.dk>
Subject: Re: Intermittent crashes - xfs_repair finds no errors
Date: Fri, 24 May 2013 09:09:28 -0500	[thread overview]
Message-ID: <519F7498.8020500@sandeen.net> (raw)
In-Reply-To: <20130524151022.160656e9@harpe.intellique.com>

On 5/24/13 8:10 AM, Emmanuel Florac wrote:
> Le Fri, 24 May 2013 11:59:02 +0200
> Ole Tange <tange@binf.ku.dk> écrivait:
> 
>> # uname -a
>> Linux lemaitre 3.2.0-0.bpo.1-amd64 #1 SMP Sat Feb 11 08:41:32 UTC 2012
>> x86_64 GNU/Linux
>>
>> May 13 11:43:31 lemaitre kernel: [507964.074856] XFS (md3): metadata
>> I/O error: block 0x18dcf8 ("xfs_trans_read_buf") error 5 buf count
>> 4096

"metadata IO error" kind of speaks for itself.  And error 5 is EIO.

It looks for all the world like you are getting read errors from the device.

> What are the few previous lines of /var/log/messages before these?
> There could be some hardware related message, or some hint of corrupted
> metadata.

Yep, full dmesg might be good.

tracing on

xfs_trans_read_buf_io
and
xfs_buf_read

might give some insight if dmesg doesn't.

-Eric

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

      reply	other threads:[~2013-05-24 14:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-24  9:59 Intermittent crashes - xfs_repair finds no errors Ole Tange
2013-05-24 13:10 ` Emmanuel Florac
2013-05-24 14:09   ` Eric Sandeen [this message]

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=519F7498.8020500@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=eflorac@intellique.com \
    --cc=tange@binf.ku.dk \
    --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