threads / discuss / 51533

2.22 issue across samba

Subject: 2.22 issue across samba

## tl;dr

2 messages between Jul 26, 2019 and Jul 29, 2019.

replies: 1people: 2as markdown or json

Gary Poli· Jul 26, 2019, 20:15 UTC · lore

Hello,
	I'm running git for windows installed locally. Windows 10 Pro version 1903 OS Build 18362.239. I have a repository on a UNIX machine running AIX 7.1 TL4 SP2. I use SAMBA 3.0.23d to mount the drive for use. I upgraded to git 2.22 and am having issues. Even starting from a fresh clone of the repo, the head immediately detaches. After a few commands like status or branch it stops recognizing the repo altogether. I suspect it is having trouble reading or writing to itself; perhaps the index is getting corrupted. I reverted to git 2.14 and I'm working fine again. I've got my system admin looking into updating both AIX and SAMBA, but I thought I would report the issue here as well. Let me know if you need anything else from me. Thanks.

Gary Poli | Lead ERP Programmer o 949 509 6216 4199 Campus Drive, 9th Floor Irvine, CA 92612

This e-mail, including any accompanying attachments, may contain confidential information that is private, personal, and/or proprietary, and it is for the sole use of the intended recipient(s).  Any unauthorized review, use, distribution or disclosure by others is strictly prohibited.  If you have received this document in error, please immediately contact Gary Poli and delete all copies of this message.

Jeff King· Jul 29, 2019, 10:10 UTC · re: Gary Poli · lore

Re: 2.22 issue across samba

On Fri, Jul 26, 2019 at 08:15:49PM +0000, Gary Poli wrote:

Show 11 quoted lines

> I'm running git for windows installed locally. Windows 10 Pro version
> 1903 OS Build 18362.239. I have a repository on a UNIX machine running
> AIX 7.1 TL4 SP2. I use SAMBA 3.0.23d to mount the drive for use. I
> upgraded to git 2.22 and am having issues. Even starting from a fresh
> clone of the repo, the head immediately detaches. After a few commands
> like status or branch it stops recognizing the repo altogether. I
> suspect it is having trouble reading or writing to itself; perhaps the
> index is getting corrupted. I reverted to git 2.14 and I'm working
> fine again. I've got my system admin looking into updating both AIX
> and SAMBA, but I thought I would report the issue here as well. Let me
> know if you need anything else from me. Thanks.

I don't have any particular thoughts on what might be the cause here. But if:

  - you can reliably produce the problem on git 2.22 but not on git 2.14

and

  - you are able to build Git from source

then it would be useful to use git-bisect between those versions to find the commit introducing the problem.

-Peff