| To: | xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Crash recovery/zero-byte file question |
| From: | Josh Endries <endries@xxxxxxxxxxxxxx> |
| Date: | Fri, 17 May 2013 12:36:29 -0400 (EDT) |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <1601451892.10839.1368808313900.JavaMail.root@xxxxxxxxxxxxxxxxxx> |
| Thread-index: | klJKOiN4NXqopKgKMn/7I6+eee6hmw== |
| Thread-topic: | Crash recovery/zero-byte file question |
Hello, We have a RHEL 6.3 machine with a large XFS mount that suffered a power outage. When it came back up, it allegedly fixed itself, but now many files are zero bytes. I found a bug report/errata fix at RH that mentions something similar, which might be what we ran into. We are running a kernel that should have the fix as far as I can tell, but we definitely have zero byte files that shouldn't be. My question is: is there a way to restore this or fix it before going to backups? Is it worth it to unmount and run xfs_check or similar? Unfortunately, since the system came up and appeared to be working, some users have been using that mount point. Thanks, Josh |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Kernel 3.3 XFS: Assertion failed: xfs_trans_get_block_res(tp) > 0, Kamal Dasu |
|---|---|
| Next by Date: | Re: [PATCH v2 7/8] xfs: Add xfs_log_rlimit.[c|h], Michael L. Semon |
| Previous by Thread: | Kernel 3.3 XFS: Assertion failed: xfs_trans_get_block_res(tp) > 0, Kamal Dasu |
| Next by Thread: | Re: Crash recovery/zero-byte file question, Eric Sandeen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |