| To: | Linux fs XFS <xfs@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: XFS, empty files after a crash |
| From: | pg_xf2@xxxxxxxxxxxxxxxxxx (Peter Grandi) |
| Date: | Tue, 21 Feb 2012 16:25:30 +0000 |
| In-reply-to: | <4F4387A7.2070009@xxxxxxxxx> |
| References: | <4F4387A7.2070009@xxxxxxxxx> |
> Hi, After a crash, a lot of files on a xfs file system report > an empty size with "ls -a" but not with "du". [ ... ] It is a FAQ: http://xfs.org/index.php/XFS_FAQ#Q:_Why_do_I_see_binary_NULLS_in_some_files_after_recovery_when_I_unplugged_the_power.3F Usually it is a good idea to do a web search before reporting a problem. > Is there a way to copy back the used blocks to recover the > files ? No, because your applications told XFS that the content of those blocks could be thrown away in case of crash. It is your responsibility to ensure that your applications use 'fsync' or at least 'fsyncdata' when data should be stored permanently before a crash occurs. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [XFS updates] XFS development tree branch, master, updated. v3.2-rc1-11443-g33e0eda, xfs |
|---|---|
| Next by Date: | [RFC v4 PATCH 2/4] xfs: Add pquota fields where gquota is used., Chandra Seetharaman |
| Previous by Thread: | XFS, empty files after a crash, kfx |
| Next by Thread: | Re: XFS, empty files after a crash, Eric Sandeen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |