| To: | Eric Sandeen <sandeen@xxxxxxxxxxx>, xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: xfs_repair fails to repair, run under valgrind shows "Invalid read..." and XFS_CORRUPTION_ERROR |
| From: | Cody P Schafer <cody@xxxxxxxxxxxxxxxxxx> |
| Date: | Tue, 11 Feb 2014 12:18:32 -0800 |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <52FA840A.7090309@xxxxxxxxxxx> |
| References: | <52FA8021.9050604@xxxxxxxxxxxxxxxxxx> <52FA840A.7090309@xxxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 |
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). |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: xfs_repair fails to repair, run under valgrind shows "Invalid read..." and XFS_CORRUPTION_ERROR, Eric Sandeen |
|---|---|
| Next by Date: | Re: xfs_repair fails to repair, run under valgrind shows "Invalid read..." and XFS_CORRUPTION_ERROR, Dave Chinner |
| Previous by Thread: | Re: xfs_repair fails to repair, run under valgrind shows "Invalid read..." and XFS_CORRUPTION_ERROR, Eric Sandeen |
| Next by Thread: | Re: xfs_repair fails to repair, run under valgrind shows "Invalid read..." and XFS_CORRUPTION_ERROR, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |