https://bugzilla.novell.com/show_bug.cgi?id=742436 https://bugzilla.novell.com/show_bug.cgi?id=742436#c1 Guido Berhörster changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Critical |Normal --- Comment #1 from Guido Berhörster 2012-01-20 13:37:21 UTC --- (In reply to comment #0)

Errors copying large number of files from external USB. Display of these errors corrupted.

Reproducible: Didn't try

Steps to Reproduce: 1.Connect USB HD 2.Copy large number of files to onboard HD 3. Actual Results: Following error report given:

2┴╚Ä ºƒ┘.╟: Error splicing file: Input/output error 2┴╚Ä ºƒ┘.╟: Error stating file '/media/Backup/../Å9HÇ N┬╡.`╡╨': Input/output error

Expected Results: No errors copying files, ideally. But since errors occurred, that those errors be displayed in readable form.

Used PCManFM to copy files. The dialogue reporting the file copy errors did however appear to be part of the generic file copying mechanism - i.e. titled "Finished" and containing the following information:

" Copying files [given files] To: /home/usrname Processing: Progress: Time remaining: Some Errors occured: "

The [...] in the erroneous filename location in the given results entered above in 'Expected Results' is my own addition in place of the actual filename location given apparently correctly by the file system.

I don't understand this part, are you using Thunar (the native Xfce filemanager) or PCManFM?

The filename itself is obscured (assuming the corrupted characters did not in fact obscure a host of errors), but there were no errors recorded in files sent to the given location when they were put there in the first place. Some 40Gb of

The filename and the containing directory are important here. Can you please do the following: * try to reproduce the issue by opening the containing directory in Thunar and try to copy it somewhere, then take a screenshot of the error dialog and attach it here * execute "gvfs-ls -lh /media/Backup/..." in a terminal ("..." replaced with the actual containing directory) and attach the output here * execute "gvfs-copy /media/Backup/.../* /some/destination/dir" in a terminal ("..." replaced with the actual containing directory and "/some/destination/dir" with any temporary destination directory) and attach the output here * attach a copy of /var/log/messages after doing the above

files were transferred. The only given errors are those copied above. I can't remember how the disk was formatted. It was perhaps NTFS, but was certainly formatted and the files copied from Ubuntu. Would someone tell me how I can check the filesystem of the disk from openSUSE, I'm afraid it's not something I know how to do.

With most filesystems corruption can take place silently so you might only notice it when you read it back. In order to determine the filesystem you can run mount | grep /media/Backup in a terminal assuming the fs is mounted on /media/Backup as indicated by the error message above. If it is NTFS you can only really repair it from Windows, for other filesystems might be able to use fsck in order to detect and repair errors.

I've marked this is a critical bug because, though I have not yet made any attempt to repeat it, it involves errors copying data and the corruption of data reporting those errors. That's pretty serious from where I'm sitting.

This looks like a corrupt filesystem rather than a problem with PCManFM or Thunar/exo/gvfs, the above "garbage" are actually filenames read from the corrupt filesystem and the error message itself is readable. 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'). -- 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.

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.

https://bugzilla.novell.com/show_bug.cgi?id=742436 https://bugzilla.novell.com/show_bug.cgi?id=742436#c5 Guido Berhörster changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #5 from Guido Berhörster 2012-01-20 18:53:13 UTC --- (In reply to comment #3)

...

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.

That's nothing unusual, a few flipped bits when adding/removing directory entries are probably enough to have arbitrary files disappear or bogus files appear.

Thanks again for your help. I am sorry to have wasted your time.

No problem. -- 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.