search

guberm / tortoisegit

Automatically exported from code.google.com/p/tortoisegit
0 stars 0 forks source link

"Failed to checkout file" error when trying to compare with base from commit window #2491

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Summary: "Failed to checkout file" error when trying to compare with base from 
commit window

What steps will reproduce the problem?
1. open commit window with at least one modified file
2. doubleclick on modified file or use return key to compare with base

What is the expected output? What do you see instead?
Expected: TortoiseMerge opens and shows differences
Actual: the following error appears:
"Failed to checkout file <gitfile> of revision <revision> to <tempfile>.
libgit2 returned: Could not create file."
(actual paths replaced with placeholders)

What version of TortoiseGit and msysgit are you using? On
what operating system?
-TortoiseGit 1.8.14.0 (C:\Program Files\TortoiseGit\bin)
(previous version 1.8.13.0 was affected too)
-git version 1.9.5.msysgit.0 (C:\Program Files (x86)\Git\bin)

Case 1:
-Windows 7 Ultimate 64bit
-Primary harddrive (containing the temp dir) is an SSD
-Secondary harddrive (containing the repo) is a regular harddrive
-Intel Core i5-2500K (quadcore)

Case 2:
-Windows 7 Professional 64bit
-Primary harddrive (containing the temp dir and repo) is an SSD
-Intel Core i7-4600U (quadcore)

Please provide any additional information below.
-The error appears irregularly, on average about half the times the "compare 
with base" action is initiated
-The error can appear several times in a row for the same file when initiating 
"compare with base" over and over again, until it finally succeeds
-When Process Monitor (v3.05) is open and capturing events, the error happens a 
lot less frequently (maybe 1 in 50 cases?) but can still happen

Original issue reported on code.google.com by chvoge...@gmail.com on 16 Apr 2015 at 9:31

Attachments:

GoogleCodeExporter commented 9 years ago 
I managed to narrow down the issue a bit further:
-The error seems to only occur when the backup service of Altaro BackupFS is 
running (present on machine mentioned as "Case 1").
-The machine mentioned as "Case 2" doesn't seem to be affected at all (memory 
served me wrong?)

Altaro BackupFS monitors the primary drive for any file changes but I never had 
any similar issues with other software so far.

Original comment by chvoge...@gmail.com on 16 Apr 2015 at 9:51

GoogleCodeExporter commented 9 years ago 
Do you have issues with other software for creating files, too?
Could you please try to collect a procmon log containing the issue?

Original comment by sstrickr...@googlemail.com on 3 May 2015 at 12:05