Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*XFS\,\s+empty\s+files\s+after\s+a\s+crash\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*XFS\,\s+empty\s+files\s+after\s+a\s+crash\s*$/: 11 ]

Total 11 documents matching your query.

1. XFS, empty files after a crash (score: 1): Author: kfx <kadafax@xxxxxxxxx>; Date: Tue, 21 Feb 2012 13:01:43 +0100; 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 us; /archives/xfs/2012-02/msg00517.html (8,284 bytes)
2. Re: XFS, empty files after a crash (score: 1): Author: pg_xf2@xxxxxxxxxxxxxxxxxx (Peter Grandi); Date: Tue, 21 Feb 2012 16:25:30 +0000; 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; /archives/xfs/2012-02/msg00524.html (7,701 bytes)
3. Re: XFS, empty files after a crash (score: 1): Author: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>; Date: Tue, 21 Feb 2012 11:39:23 -0600; What was the nature of the crash? Kernel panic? Power failure? Other? Do you have have backups of previously existing files that are now shown as zero size? If so delete and restore, maybe just overw; /archives/xfs/2012-02/msg00536.html (8,579 bytes)
4. Re: XFS, empty files after a crash (score: 1): Author: Eric Sandeen <sandeen@xxxxxxxxxxx>; Date: Tue, 21 Feb 2012 21:18:55 -0600; He seems to be reporting a different problem. In the FAQ case above, one would get a file but "it has is a size but no extents " - i.e. ls -l would show 1M, but du would show 0, and no extents are al; /archives/xfs/2012-02/msg00538.html (9,059 bytes)
5. Re: XFS, empty files after a crash (score: 1): Author: "Nathaniel W. Turner" <nate@xxxxxxxxxxxxxxx>; Date: Thu, 23 Feb 2012 14:38:25 -0500; I have noticed that xfs_bmap (which uses the ioctl bmap interface) will not report extents after EOF. There probably *are* extents allocated to this file, but they are not being reported by xfs_bmap.; /archives/xfs/2012-02/msg00553.html (8,660 bytes)
6. Re: XFS, empty files after a crash (score: 1): Author: kadafax@xxxxxxxxx; Date: Thu, 23 Feb 2012 21:07:27 +0100; kfx, try getting the inode number of the file (via stat or ls -i) and then doing something like this: xfs_db -r $DEV -c "inode $INO" -c "bmap" data offset 0 startblock 1881705728 (7/2657536) count 64; /archives/xfs/2012-02/msg00554.html (9,473 bytes)
7. Re: XFS, empty files after a crash (score: 1): Author: "Nathaniel W. Turner" <nate@xxxxxxxxxxxxxxx>; Date: Thu, 23 Feb 2012 17:15:23 -0500; kfx, try getting the inode number of the file (via stat or ls -i) and then doing something like this: xfs_db -r $DEV -c "inode $INO" -c "bmap" data offset 0 startblock 1881705728 (7/2657536) count 64; /archives/xfs/2012-02/msg00555.html (9,351 bytes)
8. Re: XFS, empty files after a crash (score: 1): Author: kadafax@xxxxxxxxx; Date: Fri, 24 Feb 2012 11:21:25 +0100; kfx, try getting the inode number of the file (via stat or ls -i) and then doing something like this: xfs_db -r $DEV -c "inode $INO" -c "bmap" data offset 0 startblock 1881705728 (7/2657536) count 64; /archives/xfs/2012-02/msg00561.html (11,039 bytes)
9. Re: XFS, empty files after a crash (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Mon, 27 Feb 2012 12:04:02 +1100; That doesn't seem right: $ ls -l foobar -rw-- 1 root root 0 Feb 27 11:54 foobar $ du foobar 1024 foobar $ du --apparent-size foobar 0 foobar $ xfs_bmap foobar foobar: 0: [0..2047]: 255169872..2551719; /archives/xfs/2012-02/msg00589.html (9,366 bytes)
10. Re: XFS, empty files after a crash (score: 1): Author: kadafax@xxxxxxxxx; Date: Mon, 27 Feb 2012 09:43:42 +0100; 27460 myfile 0 myfile myfile: no extents That doesn't seem right: $ ls -l foobar -rw-- 1 root root 0 Feb 27 11:54 foobar $ du foobar 1024 foobar $ du --apparent-size foobar 0 foobar $ xfs_bmap foobar; /archives/xfs/2012-02/msg00596.html (11,569 bytes)
11. Re: XFS, empty files after a crash (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Tue, 28 Feb 2012 12:39:25 +1100; ..... ..... ..... .... .... Ok, so there's an extent there, but xfs_bmap is not showing it because it isn't a preallocation but rather a normal extent. What this indicates is that the inode size was; /archives/xfs/2012-02/msg00607.html (10,557 bytes)

Current List: 1 - 11
Page: [1]