Bug 452682

Summary: KRUSADER: Copying to drives or network shares that report wrong free space should have a override option (force copy)
Product: [Applications] krusader Reporter: m9havock
Component: net-connectionAssignee: Krusader Bugs Distribution List <krusader-bugs-null>
Status: CONFIRMED ---    
Severity: wishlist CC: krusader-bugs-null, voidpointertonull+bugskdeorg
Priority: NOR    
Version First Reported In: 2.7.2   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description m9havock 2022-04-16 20:16:20 UTC 
SUMMARY
When attempting to copy files/directory from a source to a target, if the target space is lower than the size of the copy,
Krusader reports the error but does not permit other options to make it happen.
eg. there are times where Samba shares report the wrong free space, there is enough space on the drive.

STEPS TO REPRODUCE
1.  attempt to copy a file/directory that is larger than the free space on target
2. error message popup , "free space is less than required" 
3. fail

OBSERVED RESULT
fail

EXPECTED RESULT
1. have override and force copy options in the error prompt , or pre copy prompt
2. settings option or command-line switch to ignore or prompt action
3. ignore issues , like "mc" LOL

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Pedro V 2024-01-24 02:24:04 UTC 
There isn't even a need for wrong free space reporting, I ran into the frustrating lack of this feature in a different context.
Wanted to update a large directory with rsync, but desired to have a backup first both for safety and for checking differences later. Given that I'm using Btrfs, I opted to (ab)use CoW by doing a "ghetto backup" by just simply copying the whole directory as reflinks are quite cheap. Problem was that Krusader figured that I don't have the hundreds of GiBs of free space it would take to make a copy without reflinks, so it just didn't let me do that.

Bonus:
It's sometimes undesired to go through the files to begin with as that could introduce a large delay before starting to do the desired copy operation, and if that's not done, then there's obviously no checking for space.

If I remember well I observed these solutions in Total Commander:
- The free space problem could be just ignored as it's requested here
- The initial enumeration of files could be interrupted so the user could get rid of the extra feature conveniently
- The initial enumeration of files could be completely disabled