https://bugs.kde.org/show_bug.cgi?id=298976 David Faure changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |coolo@kde.org --- Comment #1 from David Faure --- I think this is because the new file is being written out as "bigfile.part" during the copy, and renamed to "bigfile" at the end of the copy? This is actually a feature, to avoid losing the file completely in case of a write error. But indeed it creates an issue in the case where the destination filesystem isn't big enough for both files. I don't see a good solution to the issue... we can detect this case, but then what? If we overwrite the file upfront, we lose everything (on the destination) if something happens (power cut, forced unplugging, kernel oops, etc.) -- You are receiving this mail because: You are watching all bug changes.