Git development
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Jhair Tocancipa Triana <jhair.tocancipa@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: fatal: cannot store pack file (git 1.6.0.2 + sshfs)
Date: Wed, 24 Sep 2008 09:34:00 -0700	[thread overview]
Message-ID: <20080924163400.GU3669@spearce.org> (raw)
In-Reply-To: <87iqsmy8q7.fsf@sms.ed.ac.uk>

Jhair Tocancipa Triana <jhair.tocancipa@gmail.com> wrote:
> I'm getting the following when running git on a partition mounted with
> sshfs:
> 
> $ git pull
...
> error: unable to write sha1 filename .git/objects/pack/pack-dc5c3614e795918f457a2f98a58f10134ebf246b.pack: Operation not permitted
> fatal: cannot store pack file
> fatal: index-pack failed
> 
> git pull worked fine in the same repository yesterday (new files where
> committed in the meantime).
> 
> I'm not sure if this is a problem in git or in sshfs (or somewhere
> else).

Its the size of the fetch.  The day before you probably had a smaller
number of objects downloaded (<100) so Git used unpack-objects
instead of index-pack.  Yesterday it was a larger download (>100),
so it used index-pack.

In 1.6.0.2 index-pack writes a temporary file to .git/objects but
later tries to rename it into .git/objects/pack.  That renaming
must not be working on sshfs.

Latest "master" has a change from Pasky (8b4eb6b6 "Do not perform
cross-directory renames") that should fix this issue.  Or just
don't use sshfs.  Or teach sshfs to rename across directories.

-- 
Shawn.

  reply	other threads:[~2008-09-24 16:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-23 19:15 fatal: cannot store pack file (git 1.6.0.2 + sshfs) Jhair Tocancipa Triana
2008-09-24 16:34 ` Shawn O. Pearce [this message]
2008-09-24 17:57   ` Nathan W. Panike
2008-09-24 20:05     ` Jhair Tocancipa Triana

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080924163400.GU3669@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=jhair.tocancipa@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox