GNOME Bugzilla – Bug 389828
Nautilus can leave half-copied files on the target
Last modified: 2017-09-01 22:28:20 UTC
That bug has been opened on https://launchpad.net/distros/ubuntu/+source/nautilus/+bug/67691 "If a file move/copy fails half way through (eg due to volume full error), Nautilus advises there was an error but does not try to delete the half-copied file, leaving the impression to a user on the target file system that the file was successfully copied."
This is serious stuff! I was about to delete some important files thinking that I had completely copied each one of them, but in reality Natalius had left partial copies in the Copy destination. Please fix this or at the very very least put a huge warning message box when the directory/file copy is cancelled by the user! I have: Ubuntu 9.04 I read the original bug report on Launchpad (https://launchpad.net/distros/ubuntu/+source/nautilus/+bug/67691 ) and it exactly describes the behavior I experience with Natalius. I start a directory copy of big files, cancel mid-way, and expect the Windows behavior of the partial file to be automatically deleted, so that if I start the whole directory copy again, I can answer Natalius to Skip All existing files.
Please dont completely remove this "feature". My use case, when i have a slightly corrupted CD/DVD/usb disk and i am copying a big video file from it to my pc, on windows it gets stuck in middle gives error and i cant view any of it. In ubuntu, atleast some part of the file is copied and then error is given out, and i can still view a portion of the video which is great i think.
*** Bug 613469 has been marked as a duplicate of this bug. ***
*** Bug 610593 has been marked as a duplicate of this bug. ***
Nautilus 2.30.1 - now also clicking cancel on a copy OR move operation leaves an incomplete file. While I/O errors are fairly uncommon, now this is affecting daily work. @Praveen Thirukonda: Nautilus is not a data rescue tool, dd is far more suited.
*** Bug 654571 has been marked as a duplicate of this bug. ***
A question, why is this bug unconfirmed? There many reports of this bug and it is very easy to reproduce
There seems to be a lot of duplicate bugs and there seems to be a solution for bug #403652 - https://bugzilla.gnome.org/show_bug.cgi?id=403652 Can someone mark this (or 403652) as a duplicate? This seems to have been resolved.
*** This bug has been marked as a duplicate of bug 403652 ***