From: Jeff King <peff@peff.net>
To: Tomas Pospisek <tpo@sourcepole.ch>
Cc: git@vger.kernel.org
Subject: Re: Bug? file at the same time being deleted and not registered
Date: Mon, 24 May 2010 04:49:33 -0400 [thread overview]
Message-ID: <20100524084932.GA21051@coredump.intra.peff.net> (raw)
In-Reply-To: <alpine.DEB.2.00.1005241027580.8425@tpo-laptop>
On Mon, May 24, 2010 at 10:29:02AM +0200, Tomas Pospisek wrote:
> >If it's empty or 32 bytes, then that explains what status is reporting
> >(but the question still remains how we got into that state).
>
> There's no .git/index file there:
>
> $ ls -l .git/
> total 36
> drwxr-xr-x 2 tpo tpo 4096 2010-05-23 21:36 branches
> -rw-r--r-- 1 tpo tpo 4 2010-05-23 21:36 COMMIT_EDITMSG
> -rw-r--r-- 1 tpo tpo 73 2010-05-23 21:36 description
> -rw-r--r-- 1 tpo tpo 23 2010-05-23 21:36 HEAD
> drwxr-xr-x 2 tpo tpo 4096 2010-05-23 21:36 hooks
> drwxr-xr-x 2 tpo tpo 4096 2010-05-23 21:36 info
> drwxr-xr-x 3 tpo tpo 4096 2010-05-23 21:36 logs
> drwxr-xr-x 7 tpo tpo 4096 2010-05-24 09:26 objects
> drwxr-xr-x 4 tpo tpo 4096 2010-05-23 21:36 refs
Thanks. That means "git status" is at least reporting the right thing.
Now we just need to figure out why, when the strace of commit shows it
being written and renamed into place, the index file is missing.
I tried setting up a simple mhddfs mount to reproduce your problem, but
everything works fine for me. What version of mhddfs are you using? I'm
using version 0.1.28. I wonder if git is somehow triggering an mhddfs
bug. Looking through the svn logs for mhddfs, between 0.1.27 and 0.1.28,
there is a commit with message "fixed rename bug".
-Peff
next prev parent reply other threads:[~2010-05-24 8:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-23 21:09 Bug? file at the same time being deleted and not registered Tomas Pospisek
2010-05-23 23:44 ` Jeff King
2010-05-24 8:02 ` Tomas Pospisek
2010-05-24 8:24 ` Jeff King
2010-05-24 8:29 ` Tomas Pospisek
2010-05-24 8:49 ` Jeff King [this message]
2010-05-24 9:26 ` Tomas Pospisek
2010-05-24 10:32 ` Tomas Pospisek
2010-05-24 14:46 ` Tomas Pospisek
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=20100524084932.GA21051@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=tpo@sourcepole.ch \
/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