# [BUG] Using git-completion with automounted home directories causes bogus NFS mount requests 2 messages from 2010-06-17 to 2010-06-17. Participants: Cesar Crusius, Thomas Rast. Thread: https://gitlist.dev/t/24144 ## Cesar Crusius, 2010-06-17 19:32 Subject: [BUG] Using git-completion with automounted home directories causes bogus NFS mount requests Message-ID: URL: https://gitlist.dev/e/B0356A858DE69744B8977A67332BFB2C1FE9CDAD%40dc1.mv.cariden.com ``` Hi all, I have tried this with various versions of .git-completion, including the most recent one as of today, and whenever I have __git_ps1 in my bash prompt, I get messages like this: Jun 17 12:05:14 sunray automountd[471]: [ID 834250 daemon.error] Mount of :/export/home/.git on /home/.git: No such file or directory Jun 17 12:05:14 sunray automountd[471]: [ID 834250 daemon.error] Mount of :/export/home/objects on /home/objects: No such file or directory on /var/adm/messages every time a prompt is printed from the home directory (~). When I am in any subdirectory of ~ this does not happen. This is probably a result of git/git-completion trying to access the directories above, and automount trying to get them from the server (we're in an NFS home environment, with wildcard automounts in auto_home). - Cesar ``` ## Thomas Rast, 2010-06-17 20:02 Subject: Re: [BUG] Using git-completion with automounted home directories causes bogus NFS mount requests Message-ID: <201006172202.54879.trast@student.ethz.ch> URL: https://gitlist.dev/e/201006172202.54879.trast%40student.ethz.ch In-Reply-To: ``` Cesar Crusius wrote: > Hi all, > > I have tried this with various versions of .git-completion, > including the most recent one as of today, and whenever I have > __git_ps1 in my bash prompt, I get messages like this: > > Jun 17 12:05:14 sunray automountd[471]: [ID 834250 daemon.error] Mount of :/export/home/.git on /home/.git: No such file or directory [...] > This is probably a result of git/git-completion trying to access the > directories above, and automount trying to get them from the server > (we're in an NFS home environment, with wildcard automounts in > auto_home). It's not a bug. Git repositories have only one .git metadata directory at the root of the repo. How could git possibly detect where the repository is, if not by scanning each directory up to the root for a .git entry? For a workaround, set GIT_CEILING_DIRECTORIES (available since 1.6.0), see git(1). The next released version will most likely default to not searching across mount points thanks to commit 8030e44 (Add support for GIT_ONE_FILESYSTEM, 2010-03-17). -- Thomas Rast trast@{inf,student}.ethz.ch ```