Summary: | Check sum does not like working with 4 files large files | ||
---|---|---|---|
Product: | [Applications] kleopatra | Reporter: | Kevin Jaeger <jetech> |
Component: | general | Assignee: | Andre Heinecke <aheinecke> |
Status: | ASSIGNED --- | ||
Severity: | grave | CC: | aheinecke, eugrish, mutz, pralltgarantiert |
Priority: | NOR | ||
Version: | 2.2.0 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Microsoft Windows | ||
Latest Commit: | Version Fixed In: |
Description
Kevin Jaeger
2014-10-30 00:55:55 UTC
I'm facing that same issue with Kleopatra. (Windows 7 HP 64-bit). I actually installed Gpg4win 2.2.3. The error messages that I get read as follows: "Failed to move file C:/b/the-full-path/sha256sum.txt to its final destination, sha256sum.txt: Error during rename." An empty file named "sha256sum.txtHp6836.new" gets created in the target folder. I get the error regardless of whether I invoke the checksums calculation from context menu in explorer (GpgEX) or from the File menu in the main Kleopatra window. The error seems to occur on folders that have more than 2 GiB of data in them. I have successfully created and verified checksum files for folders of smaller size. Thanks for your reports. I can reproduce the problem using a single 11gb file. Strangely enough signing that same file works and running sha1sum from gpg4win also works. Looks like some timeout in kleo. I can reproduce, especially comment 1: Kleopatra Version 2.2.0-gitfb4ae3d (2015-11-12) Unter KDE 4.13.3 on Windows 10 64bit (Pro), should be up to date as of 2017-01-17 Intel Core i5-4670K @ 3.4 GHz sha256sum.txtHp2692.new sha1sum.txtHp8528.new are generated for a 3.91 GB large file (4102945 KB), moving file to sha256sum.txt failed: Error renaming the file. Unfortunately the executables seem single threaded. Running "sha256sum.exe filename.iso" directly in the windows commandline gives me a checksum after 42 seconds. So it is difficult to look for a timeout. One core of my system is on 100% load. Moving the large file to an SSD does not speed this up. So I can't easily test if it is a time out or a file size problem. From a 1.67 GB (1758561 KB) large file the checksums are correctly calculated and saved. From HDD: sha256sum.exe has a run time of ~19 seconds From a USB thumbdrive on USB3: 19 seconds Same drive on USB 2: 44 s Kleopatra on USB 2: could not move file after 32 seconds But Window's USB-File-Caching let's me successfully finish a second run on the same file in under 30 seconds. (To avoid the use of cached thumbdrive data, I did my test always on a freshly plugged in drive and verified the read speed in the Windows Resource Monitor.) |