From: kfx <kadafax@gmail.com>
To: xfs@oss.sgi.com
Subject: XFS, empty files after a crash
Date: Tue, 21 Feb 2012 13:01:43 +0100 [thread overview]
Message-ID: <4F4387A7.2070009@gmail.com> (raw)
Hi,
After a crash, a lot of files on a xfs file system report an empty size
with "ls -a" but not with "du".
xfs_check and xfs_repair don't report any problem to repair (although an
internal log is used) :(
So if I understand correctly, those empty files actually use space on
the disk but are incorrectly reported as empty by the system.
Is there a way to copy back the used blocks to recover the files ?
Example for a previously not empty file:
# ls -l myfile
-rw-r--r-- 1 me me 0 2012-01-24 15:29 myfile
# du myfile
27460 myfile
# du --apparent-size myfile
0 myfile
# xfs_bmap myfile
myfile: no extents
System: Ubuntu 11.04 2.6.38-8-server x86_64
xfs_info /dev/sdc1
meta-data=/dev/sdc1 isize=256 agcount=10,
agsize=268435328 blks
= sectsz=512 attr=2
data = bsize=4096 blocks=2441215488, imaxpct=5
= sunit=128 swidth=640 blks
naming =version 2 bsize=4096 ascii-ci=0
log =internal bsize=4096 blocks=521728, version=2
= sectsz=512 sunit=8 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
Thank you
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2012-02-21 12:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 12:01 kfx [this message]
2012-02-21 16:25 ` XFS, empty files after a crash Peter Grandi
2012-02-22 3:18 ` Eric Sandeen
2012-02-23 19:38 ` Nathaniel W. Turner
2012-02-23 20:07 ` kadafax
2012-02-23 22:15 ` Nathaniel W. Turner
2012-02-24 10:21 ` kadafax
2012-02-21 17:39 ` Stan Hoeppner
2012-02-27 1:04 ` Dave Chinner
2012-02-27 8:43 ` kadafax
2012-02-28 1:39 ` Dave Chinner
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=4F4387A7.2070009@gmail.com \
--to=kadafax@gmail.com \
--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