https://bugzilla.novell.com/show_bug.cgi?id=742436
https://bugzilla.novell.com/show_bug.cgi?id=742436#c3
Mark Ballard changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |markjballard@googlemail.com
--- Comment #3 from Mark Ballard 2012-01-20 17:41:30 UTC ---
You are right, Guido. Thank you for correcting *my* error. It is not a problem
with openSUSE.
My operation appears to have retrieved two corrupted files from a backup
directory where they still reside. I have pasted a screenshot of those files as
seen on the external HD from an Ubuntu machine. You can see they carry the same
garbled names.
Earlier backups of the same directory do not contain the same files. None of
the legitimate files in the directory were corrupted. They are all intact and
they all remained intact during the copy operation after the corrupted files
appeared. It seems the corrupted files were put there in addition to the
legitimate files. It must be assumed that this was done during the file copy to
that location, which was from Ubuntu running on a machine with an erroneous RAM
module. No other known errors occurred in the transfer of about 40Gb of files.
I doubt it is necessary to carry out the commands you helpfully suggested.
Thanks also for your suggestions about the corrupt volume. The disk is
incidentally formatted vFAT.
Note that it is not possible to automatically detect such a "garbage", since the above filenames are perfectly valid (on most Unix filesystems filenames may contain any character except '/' and '\0').
Interesting. I find it curious that a RAM fault would add files. I don't want
to examine them for fear they are the result of a security breach.
Thanks again for your help. I am sorry to have wasted your time.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
