From: Emmanuel Florac <eflorac@intellique.com>
To: Sascha Askani <saskani@inovex.de>
Cc: xfs@oss.sgi.com
Subject: Re: Weird XFS Corruption Error
Date: Thu, 23 Jan 2014 15:19:43 +0100 [thread overview]
Message-ID: <20140123151943.281baa04@harpe.intellique.com> (raw)
In-Reply-To: <CDBC891F-BCF6-4B9B-ADDB-9E143973D188@inovex.de>
[-- Attachment #1.1: Type: text/plain, Size: 999 bytes --]
Le Wed, 22 Jan 2014 17:09:10 +0100
Sascha Askani <saskani@inovex.de> écrivait:
> Internal error xfs_bmbt_read_verify at line 789
...
> metadata I/O error: block 0x1f0 ("xfs_trans_read_buf_map") error 117
> numblks 8
A quick glance at the source code seems to indicate that there was an
actual CRC error (on disk) at this point, so that could be a RAID
problem;
OTOH it looks really similar to an older bug :
http://oss.sgi.com/archives/xfs/2013-02/msg00482.html
AFAIK this one could be related to the current Ubuntu LTS lvm stack...
We need Dave's advice on this one.
Was there nothing in the xfs_repair output? nothing in lost+found
either?
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-01-23 14:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 16:09 Weird XFS Corruption Error Sascha Askani
2014-01-22 23:31 ` Dave Chinner
2014-01-24 7:56 ` Sascha Askani
2014-01-24 21:52 ` Dave Chinner
2014-01-23 14:19 ` Emmanuel Florac [this message]
2014-01-23 14:29 ` Emmanuel Florac
2014-01-24 8:08 ` Sascha Askani
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=20140123151943.281baa04@harpe.intellique.com \
--to=eflorac@intellique.com \
--cc=saskani@inovex.de \
--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