Thus spake Felix Blyakher (felixb@xxxxxxx):
> On Jun 26, 2009, at 2:58 PM, Hendrik Hoeth wrote:
>> This is how I recovered (well, most of the data I had copied is
>> corrupt at the target location):
> Some files would not make it to disk when filesystem shut down. I'd
> expect that such files are short. Do you have other indication that
> the files are corrupt?
Of course the last file was short, but even several of the files that
had been copied just before are corrupt (it was a "cp -r" of a few
directories, total ~ 700 MByte, the error appeared when copying the last
directory). Those files have identical lengths as the source files, but
different md5sum. Since it's music, I can hear the corrupt positions;
they are at random positions somewhere in the files.
> Seems like no corruption on disk.
> The system detected in memory corruption and shut the filesystem
> down to avoid writing bad (meta)data to disk. I don't have answer
> for that problem, however you can continue to use the filesystem,
> and may never see this problem again.
Hmmm, at least no corruption as in "inconsistent file system", right?
Still doesn't make me feel well ... I guess I should run a memtest.
> If it happens again, it could be useful to run debug XFS, which may
> point to the problem.
It's the first time that I had problems on this system, and it has been
running continuously for 1 1/2 years now. So until today I thought it
was stable. If the memtest doesn't show anything, I'll keep an eye on
Thanks for the help,
"You have to take the most direct road to go instead of your
meeting, you have to, this one ended, leave at once the CERN
domain." (imprint on the CERN visitor ID cards)