This has happened on _rare_ occasions (rare likely because I am UPS
usually only run even series kernels on this particular machine).
But the problem is thus. I'll write to a file -- pre-existing file or,
has happened on new files as well. I write them to disk and think
Then...a _few_ days pass... (file if often recoverable from
crashes (like UPS not charged...minor details...may be getting near
Maybe just a mysterious crash no-apparent details -- but what is screwey
is that some files will be filled with binary zeros, or sections of files
will be filled with binary zeros. Huh? I know in this last case, the
croked was my fstab (slightly inconvenient) I'd edited a few _days_
was still there but filled with all zeros. Sometimes I'll find other
files and such that also are zeroed out.
Is there any circumstance where xfs wouldn't actually write something to
a few days?
Not just for xfs, but I wish there was a user command to sync all
buffers to disk on
the system. Sync used to do that but with delayed writes and multiple
schemes -- even mounting some fs's "async" so a specific program won't
slow down, but
something other than "umount" since that requires, sometimes, shutting
machine. But I know it had been 2-3 days since I wrote to that file
before the system
crashed. It might have been open for read in the middle of a send crash
testing circuits to do some wiring). Might that be a reason? Though
I've had it happen on files like ".profile", or something like that that
have been getting read but that had been changed hours or days earlier.
VERY rare, this happens, and it happens randomly -- other files I wrote
that file were fine. so I dunno what gives...
weird -- but just wanted to know if any one else has seen any such
I saw this under 2.4 patched kernels as well as the more recent 2.6.5