git/list[1] front-page[2] threads[3] people[4] search[5] about
 

git repo on NTFS mount

From
LSLukas Schubert <lukas.schubert@gmx.de>
Date
Jan 5, 2020, 00:49 UTC
Message-ID
<op.0dv9xiwp1jamlk@localhost>
Hi there,
for historical reasons, I keep the data that doesn't belong to any
specific user on a harddisk that is formatted as NTFS. Some git
repositories are there, too. Some time ago, I upgraded from Linux Mint 17
to 19.2. That upgrade brought a change in data partition's mount options.
Old:
UUID=20D0WHATEVER	/mnt/DATA	ntfs	defaults,nls=utf8,umask=000,uid=1000,windows_names
New: UUID=20D0WHATEVER	/DATA		ntfs	defaults,umask=007,gid=46

Now I want to initialize a new git repository user@xxxx:/DATA/Projects/LearnPython/wxGlade$ git init error: chmod on /DATA/Projects/LearnPython/wxGlade/.git/config.lock failed: Operation not permitted fatal: could not set 'core.filemode' to 'false'

Since there already are repos on that drive, the initialization must have worked before. But in https://www.linuxquestions.org/questions/showthread.php?p=6074034#post6074034 I've been told that using git in linux with repositories on NTFS is a recipe for disaster.

Given I change the mount options to what worked before the update, can I escape certain doom if I stick to a certain subset of git commands? Or is the cathastrophe inevitalbe due to subtle errors that culminate but stay hidden until it's too late?

Thanks
Lukas
Next: brian m. carlson
Message 1 of 2 in “git repo on NTFS mount”
  1. Lukas SchubertJan 5, 2020
  2. brian m. carlsonJan 5, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.