Skip to content

File descrip error with Version 2.23.0 #2318

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
niyshah opened this issue Sep 2, 2019 · 4 comments
Closed

File descrip error with Version 2.23.0 #2318

niyshah opened this issue Sep 2, 2019 · 4 comments

Comments

@niyshah
Copy link

niyshah commented Sep 2, 2019

Version 2.23.0 Cannot write to repositories stored on Novell NSS Drive using NetIQ Client. However, it does work with an earlier version. After reinstalling earlier version, GIT submissions started to work again with no change at all to repositories.

This issue logged simply to report a bug. Have reverted to the earlier version which is working fine.

Setup

64 Bit

$ git --version --build-options

git version 2.9.3.windows.1
sizeof-long: 4
  • Which version of Windows are you running? Vista, 7, 8, 10? Is it 32-bit or 64-bit?
$ cmd.exe /c ver

Microsoft Windows [Version 10.0.18362.295]
  • What options did you set as part of the installation? Or did you choose the
    defaults?

Defaults


** insert your machine's response here **
  • Any other interesting things about your environment that might be related
    to the issue you're seeing?

Using NetIQ Client to map NSS Network drives to local Windows drives.

Details

git gui update-ref failed cannot update the ref HEAD

@PhilipOakley
Copy link

Are you able to do any level of debugging? E.g bisecting the commits.

@dscho
Copy link
Member

dscho commented Sep 2, 2019

@niyshah please note that you left preciously little information to work with. If you are not able to provide more information about the problem (like, full logs, a minimal example reproducing the issue, preferably as a shells script), you will be left with debugging this on your own, or worse: it will remain broken for you and you won't be able to upgrade to newer Git for Windows versions, even if vulnerabilities are fixed. In other words: it is in your best interest to put more effort into the resolution of this bug, there are enough people willing to help you.

@niyshah
Copy link
Author

niyshah commented Sep 4, 2019

In answer to the questions posed above. I am happy to do some debugging if directed on how. I use GIT, but don't fully understand all its in and outs.

The problem is probably not related to GIT itself, rather the file open procedure being used. I've seen similar problems with other software that is designed not to work on network drives. Even though the NetIQ client makes a network path look like and behave like a local drive, it doesn't fool all software. I believe this is the root of the issue.

I'm going on leave for two weeks, however, when I return, I'll happily do some tests using a UNC path, CIFS path and local paths to get the results from each. Just for context, I store almost nothing locally on my development workstations. All projects repositories etc are stored on network drives. (Windows corrupts itself way too often for my liking. When this happens I simply revert to a saved snapshot and all my development files are safe on the network.) I've never had an issue until I installed the latest version of GIT.

So happy to contribute more to this issue, once I'm back in late September.

@niyshah niyshah closed this as completed Sep 4, 2019
@jearld

This comment has been minimized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants