From: Cody P Schafer <cody@linux.vnet.ibm.com>
To: Eric Sandeen <sandeen@sandeen.net>, xfs@oss.sgi.com
Subject: Re: xfs_repair fails to repair, run under valgrind shows "Invalid read..." and XFS_CORRUPTION_ERROR
Date: Tue, 11 Feb 2014 12:18:32 -0800 [thread overview]
Message-ID: <52FA8598.1060805@linux.vnet.ibm.com> (raw)
In-Reply-To: <52FA840A.7090309@sandeen.net>
On 02/11/2014 12:11 PM, Eric Sandeen wrote:
> On 2/11/14, 1:55 PM, Cody P Schafer wrote:
>> xfsprogs version: v3.2.0-alpha2-14-g6e79202
>>
>> uname: Linux hostname 3.11.10-301.fc20.ppc64 #1 SMP Tue Dec 10 00:35:15 MST 2013 ppc64 POWER8 (architected), altivec supported CHRP IBM,8286-42A GNU/Linux
>>
>> full log attached.
>
> Yikes, that's one destroyed filesystem. What happened?
>
Well, initially? no idea. This is the second time that the repair
failed, so the first one may not have been too kind to the system. The
fs still mounts fine (or did before this particular failed repair), but
has random file corruption (pieces of files get replaced with other
junk). Most of the time without any XFS_CORRUPTION errors showing up in
dmesg (though they did appear a few times in the past).
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-02-11 20:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 19:55 xfs_repair fails to repair, run under valgrind shows "Invalid read..." and XFS_CORRUPTION_ERROR Cody P Schafer
2014-02-11 20:11 ` Eric Sandeen
2014-02-11 20:18 ` Cody P Schafer [this message]
2014-02-11 20:43 ` Dave Chinner
2014-02-11 21:06 ` Cody P Schafer
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=52FA8598.1060805@linux.vnet.ibm.com \
--to=cody@linux.vnet.ibm.com \
--cc=sandeen@sandeen.net \
--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