[GH-ISSUE #1152] Cannot do `git status` or `git push` with repo inside a mounted folder #603

New issue

Closed

opened 2026-03-04 01:47:06 +03:00 by kerem · 3 comments

kerem commented

2026-03-04 01:47:06 +03:00

Owner

Originally created by @echyam on GitHub (Sep 11, 2019).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1152

Additional Information

Reproduce:

I first mounted an s3 folder.
Within the s3 folder, I cloned a private repo.
touch an empty file
git add <emptyfile>
git status or git commit -m "add empty file"
error (same error for both commands):

# git status
error: bad index file sha1 signature
fatal: index file corrupt

Version of s3fs being used (s3fs --version)

# s3fs --version
Amazon Simple Storage Service File System V1.85 (commit:81102a5) with OpenSSL
Copyright (C) 2010 Randy Rizun <rrizun@gmail.com>
License GPL2: GNU GPL version 2 <https://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse)

# pkg-config --modversion fuse   
2.9.7

Kernel information (uname -r)

# uname -r
4.15.0-1035-aws

GNU/Linux Distribution, if applicable (cat /etc/os-release)

# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
NAME="Debian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

s3fs command line used, if applicable

N/A

/etc/fstab entry, if applicable

N/A?

s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs)

if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages

Details about issue

see Additional Information section
screenshot:
Screen Shot 2019-09-11 at 2 21 33 PM

Originally created by @echyam on GitHub (Sep 11, 2019). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1152 ### Additional Information Reproduce: 1. I first mounted an s3 folder. 2. Within the s3 folder, I cloned a private repo. 3. touch an empty file 4. `git add <emptyfile>` 5. `git status` or `git commit -m "add empty file"` 6. error (same error for both commands): ``` # git status error: bad index file sha1 signature fatal: index file corrupt ``` #### Version of s3fs being used (s3fs --version) ``` # s3fs --version Amazon Simple Storage Service File System V1.85 (commit:81102a5) with OpenSSL Copyright (C) 2010 Randy Rizun <rrizun@gmail.com> License GPL2: GNU GPL version 2 <https://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. ``` #### Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse) ``` # pkg-config --modversion fuse 2.9.7 ``` #### Kernel information (uname -r) ``` # uname -r 4.15.0-1035-aws ``` #### GNU/Linux Distribution, if applicable (cat /etc/os-release) ``` # cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 9 (stretch)" NAME="Debian GNU/Linux" VERSION_ID="9" VERSION="9 (stretch)" ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" ``` #### s3fs command line used, if applicable N/A #### /etc/fstab entry, if applicable N/A? #### s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs) _if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages_ ``` ``` ### Details about issue see Additional Information section screenshot: <img width="619" alt="Screen Shot 2019-09-11 at 2 21 33 PM" src="https://user-images.githubusercontent.com/11476825/64737151-0e860c80-d4a1-11e9-902f-616514ccc0bc.png">

kerem closed this issue

2026-03-04 01:47:07 +03:00

kerem commented

2026-03-04 01:47:08 +03:00

Author

Owner

@gaul commented on GitHub (Sep 11, 2019):

Could you test with the latest master instead of 1.85? Specifically it includes c596441f58 which may address your symptoms.

@gaul commented on GitHub (Sep 11, 2019): Could you test with the latest master instead of 1.85? Specifically it includes c596441f5872c5309908739de66397182229123c which may address your symptoms.

kerem commented

2026-03-04 01:47:08 +03:00

Author

Owner

@gaul commented on GitHub (Feb 2, 2020):

Closing due to lack of activity.

@gaul commented on GitHub (Feb 2, 2020): Closing due to lack of activity.

kerem commented

2026-03-04 01:47:08 +03:00

Author

Owner

@eggie5 commented on GitHub (Aug 1, 2020):