From: Peter <vmail@mycircuit.org>
To: git@vger.kernel.org
Subject: Re: fatal: unable to write sha1 file git 1.6.2.1
Date: Tue, 24 Mar 2009 22:05:06 +0100 [thread overview]
Message-ID: <49C94B02.5010604@mycircuit.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0903241226570.3032@localhost.localdomain>
I consolidate from Nicolas and Linus, thanks for your help:
Currently, Git is unable to deal with files that it cannot load entirely
in memory.
What is the size of your largest file?
The biggest is 51 Mb , followed by one that is 23 MB. I was able to add
and commit a part of the dir tree where the biggest file was 14 Mb. So
there seems to be a threshold between 23 Mb and 14 Mb.
> If that is the only error message you got, then afaik the only way that
> can happen is if "close(fd)" returns an error.
>
Yes thats the only message I got.
> The only other "unable to write sha1 file" message happens if
> write_buffer() fails, but if that happens then you should also have gotten
> a
>
> file write error (<error message goes here>)
>
> message in addition to the "unable to write sha1 file".
>
> What OS? What filesystem? Are you perhaps running out of space?
>
Its Lenny Debian 5.0.0, Diskspace is ample . Filesystem is cifs ( this
is a windows 2000 share mounted with samba in a VMware Workstation
Debian client ( yes, I know ... )). Memory usage, according to htop, is
constant = 140/504 MB during the whole process until git fails.
> You could also try to apply this patch to get more information (Junio,
> maybe worth doing regardless? We should try to avoid ambiguous error
> messages that don't give full error information)
>
> Linus
> ---
> sha1_file.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/sha1_file.c b/sha1_file.c
> index 4563173..54972f9 100644
> --- a/sha1_file.c
> +++ b/sha1_file.c
> @@ -2287,7 +2287,7 @@ static void close_sha1_file(int fd)
> fsync_or_die(fd, "sha1 file");
> fchmod(fd, 0444);
> if (close(fd) != 0)
> - die("unable to write sha1 file");
> + die("error when closing sha1 file (%s)", strerror(errno));
> }
>
> /* Size of directory component, including the ending '/' */
> --
>
Will try it, thanks
Peter
next prev parent reply other threads:[~2009-03-24 21:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 18:20 fatal: unable to write sha1 file git 1.6.2.1 Peter
2009-03-24 19:30 ` Nicolas Pitre
2009-03-24 19:31 ` Linus Torvalds
2009-03-24 21:05 ` Peter [this message]
2009-03-24 22:30 ` Linus Torvalds
2009-03-24 22:42 ` Peter
2009-03-25 0:03 ` Linus Torvalds
2009-03-25 0:24 ` Jeff Layton
2009-03-24 23:35 ` Jeff Layton
2009-03-25 0:11 ` Linus Torvalds
2009-03-25 0:17 ` Steven French
2009-03-25 0:49 ` Jeff Layton
2009-03-25 10:52 ` Peter
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=49C94B02.5010604@mycircuit.org \
--to=vmail@mycircuit.org \
--cc=git@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).