git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Johnny Lee" <johnnylee194@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Error: unable to unlink ... when using "git gc"
Date: Tue, 06 Jan 2009 00:59:21 -0800	[thread overview]
Message-ID: <7vy6xohkt2.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <488807870901052300y57f59b90rdc03cc47c790b416@mail.gmail.com> (Johnny Lee's message of "Tue, 6 Jan 2009 15:00:52 +0800")

"Johnny Lee" <johnnylee194@gmail.com> writes:

> While I'm looking at these "unable to unlink" files, it seems they are
> read only:
> git@tomato:~/golf$ ls -l .git/objects/16/
> total 4
> -r--r--r-- 1 johnny johnny 26 2009-01-05 09:25
> b14f5da9e2fcd6f3f38cc9e584cef2f3c90ebe


Check "ls -ld .git/objects/16" and see if it is owned by you and writable
by you.

In sane POSIX filesystem semantics, it should not pose with problem with
respect to removal that a file is unwritable.

What counts is the writability of the parent directory.

  parent reply	other threads:[~2009-01-06  9:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-06  7:00 Error: unable to unlink ... when using "git gc" Johnny Lee
2009-01-06  7:22 ` Jeff King
     [not found]   ` <488807870901052352w585da727r6d4a1e4ca4238cab@mail.gmail.com>
2009-01-06  8:03     ` Jeff King
2009-01-06  8:09       ` Johnny Lee
2009-01-06 11:57       ` Sitaram Chamarty
2009-01-06 15:05         ` Johnny Lee
2009-01-06 15:33           ` Sitaram Chamarty
2009-01-07  5:59             ` Jeff King
2009-01-07  6:27         ` Boyd Stephen Smith Jr.
2009-01-07 10:55           ` Sitaram Chamarty
2009-01-07 12:29             ` Sitaram Chamarty
2009-01-07 15:48             ` Boyd Stephen Smith Jr.
2009-01-07 18:00               ` Sitaram Chamarty
2009-01-07 19:46                 ` Boyd Stephen Smith Jr.
2009-01-06  8:59 ` Junio C Hamano [this message]
2009-01-06  9:18   ` Johnny Lee
2009-01-06 13:27     ` Matthieu Moy

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=7vy6xohkt2.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=johnnylee194@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;
as well as URLs for NNTP newsgroup(s).