running git-update-cache --refresh on different machines on a NFS share always ends up in a lot of io/cpu/time waste · Thomas Glanzmann <hidden> · 2016-06-15
Re: running git-update-cache --refresh on different machines on a NFS share always ends up in a lot of io/cpu/time waste · Linus Torvalds <torvalds@osdl.org> · 2016-06-15
Re: running git-update-cache --refresh on different machines on a NFS share always ends up in a lot of io/cpu/time waste · Thomas Glanzmann <hidden> · 2016-06-15
Re: running git-update-cache --refresh on different machines on a NFS share always ends up in a lot of io/cpu/time waste · Linus Torvalds <torvalds@osdl.org> · 2016-06-15
[PATCH] Don't include devicenumber into INODE_CHANGED test [WAS: Re: running git-update-cache --refresh on different machines on a NFS share always ends up in a lot of io/cpu/time waste] · Thomas Glanzmann <hidden> · 2016-06-15
Alternate Patch: [PATCH] Don't include device number in cache invalidation when running on NFS · Thomas Glanzmann <hidden> · 2016-06-15
Re: Alternate Patch: [PATCH] Don't include device number in cache invalidation when running on NFS · Linus Torvalds <torvalds@osdl.org> · 2016-06-15
Re: Alternate Patch: [PATCH] Don't include device number in cache invalidation when running on NFS · Thomas Glanzmann <hidden> · 2016-06-15

running git-update-cache --refresh on different machines on a NFS share always ends up in a lot of io/cpu/time waste

From: Thomas Glanzmann <hidden>
Date: 2016-06-15 22:41:58

Hello,
I wonder why 'git-update-cache --refresh' running in the same directory
shared via NFS ends up in reindexing the whole files when running on
different machines on a NFS share.

Is there a reason for this or can it easily be fixes. I also wonder if
the locking which is used to lock the cache is 'nfs safe'.

	Thomas

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help