xfs
[Top] [All Lists]

Re: Intermittent crashes - xfs_repair finds no errors

To: Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>
Subject: Re: Intermittent crashes - xfs_repair finds no errors
From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Fri, 24 May 2013 09:09:28 -0500
Cc: Ole Tange <tange@xxxxxxxxxx>, xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20130524151022.160656e9@xxxxxxxxxxxxxxxxxxxx>
References: <CANU9nTnbA8WLK68X4yLFODiBZZgT4xX9U6fEmCHp+0+BMb6XQQ@xxxxxxxxxxxxxx> <20130524151022.160656e9@xxxxxxxxxxxxxxxxxxxx>
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
On 5/24/13 8:10 AM, Emmanuel Florac wrote:
> Le Fri, 24 May 2013 11:59:02 +0200
> Ole Tange <tange@xxxxxxxxxx> é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

<Prev in Thread] Current Thread [Next in Thread>