Messages in this thread | | | Date | Mon, 12 Jul 2004 22:24:02 -0700 | From | Chris Wedgwood <> | Subject | Re: XFS: how to NOT null files on fsck? |
| |
On Tue, Jul 13, 2004 at 03:44:52AM +0200, Bernd Eckenfels wrote:
> I can say, that nulls in files are most common at the end of > (sys)log files filing up to the next block boundary.
Ideally syslog would rewind back past an nulls when it opens files.
> ls -s compared with ls -l should make that visible?
No, unwritten extents has an on-disk place, just the data isn't written. I'm not sure if there is an easy way to tell if an extent is unritten or not, I guess you could use xfs_bmap -p if that's working right for you.
--cw
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |