# Samba NTFS error "Could not rename the lock file?"

2 messages from 2008-01-16 to 2008-01-16. Participants: Mike, Sean.
Thread: https://gitlist.dev/t/11637

## Mike, 2008-01-16 03:13

Subject: Samba NTFS error "Could not rename the lock file?"
Message-ID: <478D765B.90905@talkingspider.com>
URL: https://gitlist.dev/e/478D765B.90905%40talkingspider.com

```

git version 1.5.2.1

I have my repository on a linux server and I'm trying to create a "git 
clone" on an NTFS samba mount. So for example:

$ git clone /www/git/amflex /mnt/NTFS80gigsamba/amflex
Could not rename the lock file?
Could not rename the lock file?
Could not rename the lock file?
Could not rename the lock file?
Initialized empty Git repository in /mnt/NTFS80gigsamba/amflex/.git/
remote: Generating pack...
remote: Done counting 156 objects.
remote: Deltifying 156 objects...
remote:  100% (156/156) done
Indexing 156 objects...
remote: Total 156 (delta 58), reused 0 (delta 0)
  100% (156/156) done
Resolving 58 deltas...
  100% (58/58) done
Could not rename the lock file?
Could not rename the lock file?

This isn't permissions because I can manually create, rename, delete all 
the files on the samba mount, using the same login account, no problem.

fstab for the samba mount is:

//192.168.1.100/NTFS80gigsamba /mnt/NTFS80gigsamba 
user,auto,file_mode=0777,dir_mode=0777,credentials=/etc/samba/auth.mike,uid=dmke 
0 0

```

## Sean, 2008-01-16 04:32

Subject: Re: Samba NTFS error "Could not rename the lock file?"
Message-ID: <BAYC1-PASMTP13F08E2183200D4BDF089FAE400@CEZ.ICE>
URL: https://gitlist.dev/e/BAYC1-PASMTP13F08E2183200D4BDF089FAE400%40CEZ.ICE
In-Reply-To: <478D765B.90905@talkingspider.com>

```
On Tue, 15 Jan 2008 22:13:31 -0500
Mike <fromlists@talkingspider.com> wrote:

> git version 1.5.2.1
> 
> I have my repository on a linux server and I'm trying to create a "git 
> clone" on an NTFS samba mount. So for example:

Mike,

You may be running into an issue due to filename case insensitivity when
using NTFS over Samba.  Either way, it would be helpful if you could test
with the latest stable Git (v1.5.3.8) since the error you're hitting has
been removed and the code replaced with different logic.

Sean.

```
