[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 298976] Dolphin says "no space left on device" instead of overwrite a big file in it.
From:       David Faure <faure () kde ! org>
Date:       2012-05-10 8:51:29
Message-ID: bug-298976-17878-2cVAyBXXhD () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=298976

David Faure <faure@kde.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |coolo@kde.org

--- Comment #1 from David Faure <faure@kde.org> ---
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.
[prev in list] [next in list] [prev in thread] [next in thread]