Public bug reported:
Binary package hint: nautilus
If you try to move a number of files to another volume it removes source
files after each one is copied. This means that if you cancel the
operation in the middle you end up with your files split arbitrarily
between the source and the destination.
This is unintuitive and unlike how other systems work; the normal
approach is to copy all the files, and then only remove the source files
once you know that the copy is successful. If cancelled before the copy
is complete, then the copied files are removed. This allows the
operation to be treated as transactional --- it will either succeed
completely or fail with no side effects.
Yes, I have just lost data due to this, using the following workflow:
- attempt to move files to another volume.
- copy fails midway with I/O error.
- reinitialise destination volume.
- retry move.
- notice that it's moving fewer files than I started out with.
If moves are not going to be treated as transactional, then I'd suggest
that instead of removing files unilaterally from the source file system,
they should instead get moved to the Trash, to allow easier cleanup from
what is inherently a riskier procedure.
** Affects: nautilus (Ubuntu)
Importance: Undecided
Status: New
--
Cancelling a 'move files' operation leaves the file system inconsistent
https://bugs.launchpad.net/bugs/326030
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
