On Mon, May 12, 2003 at 07:22:13AM -0500, Steve Lord wrote:
> On Mon, 2003-05-12 at 05:23, Axel Thimm wrote:
> > I know about XFS's zeroing of files for such files that were still marked as
> > dirty when the crash occured. I wonder about two things:
> > o Why are 15-20 minutes old files also wiped out? Are the write-backs that
> > much delayed (even if there is not other FS/CPU load)?
> > o What is the best way to find these files (why aren't their names simply
> > dumped to the kernel logs)? Something like
> > find . -xdev -type f \! -empty | xargs <grep for non-zero character here>
> > What's the best expression for the last part?
> > (Red Hat 8.0 & XFS 1.2)
> > --
> > Axel.Thimm@xxxxxxxxxxxxxxxxxxx
> You need to try the current cvs kernel, there was a major rework of xfs
> sync recently which should have fixed this.
Thanks. Are zero filled files now completely avoidable, or simply
happen less often? The nicest scenario would be for files not
completly rewritten to disk at fs crash to revert to the previous
Failing that it would be good to have them pinned down in some
way. Currently I have extremely large downtimes at fs crashes due to
the checks I have to run over the fs to detect those files to get them
from backup. Maybe altering something in the inode that could be used
to flag damaged files? Or dumping the files out to the kernel logs
(the latter does not help much of course if your /var/log is hosed).
Description: PGP signature