Re: [cygwin] Cygwin's git says "error: failed to read delta-pack base object"

Re: [cygwin] Cygwin's git says "error: failed to read delta-pack base object"

[Dave Lindbergh]

>> It works fine on a local NTFS volume.
>>
>> I get the error when I do it on Z:, which is mapped to a network drive
>> (on another Windows box).
>
>It works fine for me on a network drive mounted from another Windows
>machine used via the cygdrive prefix:
>[..]
>I tried with two different mount points, one to a Cygwin-created remote
>dir, one to a Windows-created remote dir.
>
>> Is there a workaround? Why does this happen?
>
>No idea.  How do you mount the drive, e.g., what does `mount' print for
>the drive?  Or could this be a permission problem?  If all else fails
>you could try to find out what happens via strace.

Mount gives:

   Z: on /cygdrive/z type ntfs (binary,posix=0,user,noumount,auto)

It's an ordinary LAN share on another local Windows box, mapped to
drive Z: via "Map network drive" in Explorer (Win7). I have full
permissions.

You are more than welcome to read the strace output if that'll give
you a clue (it doesn't give me one). All 1.7 MBytes of it are at
http://nerdfever.com/files/strace.txt

(That comes from "strace git clone
https://github.com/nerdfever/pic32mx-bmf >strace.txt")

I'm still stumped.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: [cygwin] Cygwin's git says "error: failed to read delta-pack base object"

[Adam Dinwoodie]

On Thu, Dec 04, 2014 at 04:27:51PM -0500, Dave Lindbergh wrote:
> You are more than welcome to read the strace output if that'll give
> you a clue (it doesn't give me one). All 1.7 MBytes of it are at
> http://nerdfever.com/files/strace.txt
> 
> (That comes from "strace git clone
> https://github.com/nerdfever/pic32mx-bmf >strace.txt")
> 
> I'm still stumped.

Okay, I'm looking through this trace in the hope of finding something.
The below looks suspicious, but I'm not sufficiently familiar with
either Git or Cygwin internals to know (a) whether this is a problem at
all or (b) if it is a problem, whether it's a symptom of an earlier
problem I haven't spotted on my brief skim.

      616 12330609 [main] git 2348 unlink_nt: Trying to delete \??\Z:\pic32mx-bmf\.git\objects\30, isdir = 1
     3190 12333799 [main] git 2348 unlink_nt: Setting delete disposition on \??\Z:\pic32mx-bmf\.git\objects\30 failed, status = 0xC0000101
     6362 12340161 [main] git 2348 unlink_nt: Try-to-bin \??\Z:\pic32mx-bmf\.git\objects\30
    24341 12364502 [main] git 2348 try_to_bin: \??\Z:\pic32mx-bmf\.git\objects\30, return bin_status 3
      645 12365147 [main] git 2348 unlink_nt: Try \??\Z:\pic32mx-bmf\.git\objects\30 again
    12250 12377397 [main] git 2348 unlink_nt: Setting delete disposition on \??\Z:\pic32mx-bmf\.git\objects\30 failed, status = 0xC0000101
    22680 12400077 [main] git 2348 unlink_nt: Try \??\Z:\pic32mx-bmf\.git\objects\30 again
     8487 12408564 [main] git 2348 unlink_nt: Setting delete disposition on \??\Z:\pic32mx-bmf\.git\objects\30 failed, status = 0xC0000101
     1903 12410467 [main] git 2348 unlink_nt: Try \??\Z:\pic32mx-bmf\.git\objects\30 again
    <above two lines repeated several more times>

I'm also curious about the difference between the MinGW32 version and
the Cygwin version.  Possibly it's barking up completely the wrong tree,
but what versions of each are you running?

In the hunt for a simple test case, is it just this repository that's
causing problems, or are others being difficult too?  Specifically, I'm
wondering about a trivial repository with only a handful of objects.

Do you know anything about that 300bdeb object? In particular, is it
particularly big or unusual in some other way?

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: [cygwin] Cygwin's git says "error: failed to read delta-pack base object"

[Csaba Raduly]

On Thu, Dec 4, 2014 at 10:27 PM, Dave Lindbergh  wrote:
> I'm still stumped.

You should have stood closer to the wicket :)

Csaba
-- 
GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++
The Tao of math: The numbers you can count are not the real numbers.
Life is complex, with real and imaginary parts.
"Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds
"People disagree with me. I just ignore them." -- Linus Torvalds

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: [cygwin] Cygwin's git says "error: failed to read delta-pack base object"

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 4012 bytes --]

On Dec  4 22:42, Adam Dinwoodie wrote:
> On Thu, Dec 04, 2014 at 04:27:51PM -0500, Dave Lindbergh wrote:
> > You are more than welcome to read the strace output if that'll give
> > you a clue (it doesn't give me one). All 1.7 MBytes of it are at
> > http://nerdfever.com/files/strace.txt
> > 
> > (That comes from "strace git clone
> > https://github.com/nerdfever/pic32mx-bmf >strace.txt")
> > 
> > I'm still stumped.
> 
> Okay, I'm looking through this trace in the hope of finding something.
> The below looks suspicious, but I'm not sufficiently familiar with
> either Git or Cygwin internals to know (a) whether this is a problem at
> all or (b) if it is a problem, whether it's a symptom of an earlier
> problem I haven't spotted on my brief skim.
> 
>       616 12330609 [main] git 2348 unlink_nt: Trying to delete \??\Z:\pic32mx-bmf\.git\objects\30, isdir = 1
>      3190 12333799 [main] git 2348 unlink_nt: Setting delete disposition on \??\Z:\pic32mx-bmf\.git\objects\30 failed, status = 0xC0000101
>      6362 12340161 [main] git 2348 unlink_nt: Try-to-bin \??\Z:\pic32mx-bmf\.git\objects\30
>     24341 12364502 [main] git 2348 try_to_bin: \??\Z:\pic32mx-bmf\.git\objects\30, return bin_status 3
>       645 12365147 [main] git 2348 unlink_nt: Try \??\Z:\pic32mx-bmf\.git\objects\30 again
>     12250 12377397 [main] git 2348 unlink_nt: Setting delete disposition on \??\Z:\pic32mx-bmf\.git\objects\30 failed, status = 0xC0000101
>     22680 12400077 [main] git 2348 unlink_nt: Try \??\Z:\pic32mx-bmf\.git\objects\30 again
>      8487 12408564 [main] git 2348 unlink_nt: Setting delete disposition on \??\Z:\pic32mx-bmf\.git\objects\30 failed, status = 0xC0000101
>      1903 12410467 [main] git 2348 unlink_nt: Try \??\Z:\pic32mx-bmf\.git\objects\30 again
>     <above two lines repeated several more times>

First a sharing violation (not visible in the above snippet), then
directory not empty.

This seems to be the result of an earlier problem.  What I found in
the strace is this:

- Create file Z:\pic32mx-bmf\.git\objects\30\tmp_obj_YljwNZ

- open file, write something, close file.

- link (Z:\pic32mx-bmf\.git\objects\30\tmp_obj_YljwNZ,
	Z:\pic32mx-bmf\.git\objects\30\0bdeb2fd209d24afb865584da10b78aa8fefc4)
  succeeds.

- unlink (Z:\pic32mx-bmf\.git\objects\30\tmp_obj_YljwNZ) succeeds

- Trying to open
  Z:\pic32mx-bmf\.git\objects\30\0bdeb2fd209d24afb865584da10b78aa8fefc4
  but the file doesn't exist and NtCreateFile fails with status
  0xC0000034, STATUS_OBJECT_NAME_NOT_FOUND --> ENOENT.

- Subsequent unlink (Z:\pic32mx-bmf\.git\objects\30) fails with a
  STATUS_DIRECTORY_NOT_EMPTY --> ENOTEMPTY.

- git seems to be prepared for such a case, the parent process calls
  opendir/readdir on the directory.  Enumerating the files in
  Z:\pic32mx-bmf\.git\objects\30 shows the entries ".", ".." and
  "0bdeb2fd209d24afb865584da10b78aa8fefc4".

- Then git calls lstat on the file, which results in NtOpenFile
  returning status STATUS_OBJECT_NAME_NOT_FOUND again.

- From a POSIX POV this means "somebody else" deleted the file,
  so the dir is empty now.  Git tries to delete the directory again,
  which again results in STATUS_DIRECTORY_NOT_EMPTY --> ENOTEMPTY
  and, internally, a sharing violation which disallows to move the
  directory out of the way.

This looks suspiciously like a bug in the remote filesystem.  Link
succeeded, so there are two links to the same file in the directory.
Unlinking link 1 succeeds, so there's still one link to the file in the
directory, but link 2 is inaccessible as if the file has been deleted
completely.  Thus, a full POSIX git on this drive is broken.

Can you please run

  /usr/lib/csih/getVolInfo /cygdrive/z

and paste the output here?  Maybe I can workaround this in the next
Cygwin version.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: [cygwin] Cygwin's git says "error: failed to read delta-pack base object"

[Dave L]

On Fri, Dec 5, 2014 at 6:35 AM, Corinna Vinschen
<corinna-cygwin@cygwin.com> wrote:
>
> ...
>
> This looks suspiciously like a bug in the remote filesystem.  Link
> succeeded, so there are two links to the same file in the directory.
> Unlinking link 1 succeeds, so there's still one link to the file in the
> directory, but link 2 is inaccessible as if the file has been deleted
> completely.  Thus, a full POSIX git on this drive is broken.
>
> Can you please run
>
>   /usr/lib/csih/getVolInfo /cygdrive/z
>
> and paste the output here?  Maybe I can workaround this in the next
> Cygwin version.

 Here you go:

$ /usr/lib/csih/getVolInfo /cygdrive/Z
Device Type        : 7
Characteristics    : 10
Volume Name        : <>
Serial Number      : 1646121781
Max Filenamelength : 255
Filesystemname     : <NTFS>
Flags              : c700ff
  FILE_CASE_SENSITIVE_SEARCH  : TRUE
  FILE_CASE_PRESERVED_NAMES   : TRUE
  FILE_UNICODE_ON_DISK        : TRUE
  FILE_PERSISTENT_ACLS        : TRUE
  FILE_FILE_COMPRESSION       : TRUE
  FILE_VOLUME_QUOTAS          : TRUE
  FILE_SUPPORTS_SPARSE_FILES  : TRUE
  FILE_SUPPORTS_REPARSE_POINTS: TRUE
  FILE_SUPPORTS_REMOTE_STORAGE: FALSE
  FILE_VOLUME_IS_COMPRESSED   : FALSE
  FILE_SUPPORTS_OBJECT_IDS    : TRUE
  FILE_SUPPORTS_ENCRYPTION    : TRUE
  FILE_NAMED_STREAMS          : TRUE
  FILE_READ_ONLY_VOLUME       : FALSE
  FILE_SEQUENTIAL_WRITE_ONCE  : FALSE
  FILE_SUPPORTS_TRANSACTIONS  : FALSE

Thanks for looking into this.  FWIW, @Kai on StackExchange has been
able to reproduce the problem. See last comment here:

http://stackoverflow.com/questions/27156413/how-to-configure-cygwin-git-for-two-factor-authentication-at-github-com/27176547?noredirect=1#comment43088817_27176547

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: [cygwin] Cygwin's git says "error: failed to read delta-pack base object"

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 2077 bytes --]

On Dec  5 12:39, Dave L wrote:
> On Fri, Dec 5, 2014 at 6:35 AM, Corinna Vinschen
> <corinna-cygwin@cygwin.com> wrote:
> >
> > ...
> >
> > This looks suspiciously like a bug in the remote filesystem.  Link
> > succeeded, so there are two links to the same file in the directory.
> > Unlinking link 1 succeeds, so there's still one link to the file in the
> > directory, but link 2 is inaccessible as if the file has been deleted
> > completely.  Thus, a full POSIX git on this drive is broken.
> >
> > Can you please run
> >
> >   /usr/lib/csih/getVolInfo /cygdrive/z
> >
> > and paste the output here?  Maybe I can workaround this in the next
> > Cygwin version.
> 
>  Here you go:
> 
> $ /usr/lib/csih/getVolInfo /cygdrive/Z
> Device Type        : 7
> Characteristics    : 10
> Volume Name        : <>
> Serial Number      : 1646121781
> Max Filenamelength : 255
> Filesystemname     : <NTFS>
> Flags              : c700ff
>   FILE_CASE_SENSITIVE_SEARCH  : TRUE
>   FILE_CASE_PRESERVED_NAMES   : TRUE
>   FILE_UNICODE_ON_DISK        : TRUE
>   FILE_PERSISTENT_ACLS        : TRUE
>   FILE_FILE_COMPRESSION       : TRUE
>   FILE_VOLUME_QUOTAS          : TRUE
>   FILE_SUPPORTS_SPARSE_FILES  : TRUE
>   FILE_SUPPORTS_REPARSE_POINTS: TRUE
>   FILE_SUPPORTS_REMOTE_STORAGE: FALSE
>   FILE_VOLUME_IS_COMPRESSED   : FALSE
>   FILE_SUPPORTS_OBJECT_IDS    : TRUE
>   FILE_SUPPORTS_ENCRYPTION    : TRUE
>   FILE_NAMED_STREAMS          : TRUE
>   FILE_READ_ONLY_VOLUME       : FALSE
>   FILE_SEQUENTIAL_WRITE_ONCE  : FALSE
>   FILE_SUPPORTS_TRANSACTIONS  : FALSE

Standard NTFS, it seems.

> Thanks for looking into this.  FWIW, @Kai on StackExchange has been
> able to reproduce the problem. See last comment here:

I don't know what I can do here.  This works fine for me and as long as
I can't reproduce the issue...  Could that be related to sharing
permissions?!?


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: [cygwin] Cygwin's git says "error: failed to read delta-pack base object"

[Andrey Repin]

Greetings, Dave Lindbergh!

>> [copy off list, because the sourceware system admins throws temper tantrums]
>>> -----Original Message-----
>>> From: Dave L
>>> Sent: Wednesday, December 03, 2014 15:30
>>>
>>> ...but the git from github.com works fine.
>>>
>>> I installed Cygwin's version of git, and get this:
>>>
>>>     $ git clone https://github.com/nerdfever/pic32mx-bmf
>>>     Cloning into 'pic32mx-bmf'...
>>>     remote: Counting objects: 12, done.
>>>     remote: Total 12 (delta 0), reused 0 (delta 0)
>>>     error: failed to read delta-pack base object
>>>     300bdeb2fd209d24afb865584da10b78aa8fefc4
>>>     fatal: unpack-objects failed
>>
>> What file system are you on? Local NTFS or remote?

> Aha - you're right.

> It works fine on a local NTFS volume.

> I get the error when I do it on Z:, which is mapped to a network drive
> (on another Windows box).

> Is there a workaround? Why does this happen?

Is this Z: drive on a machine in the same domain?


--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 05.12.2014, <07:58>

Sorry for my terrible english...


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: [cygwin] Cygwin's git says "error: failed to read delta-pack base object"

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 2022 bytes --]

On Dec  3 18:07, Dave Lindbergh wrote:
> On Wed, Dec 3, 2014 at 3:42 PM, Jason Pyeron <jpyeron@pdinc.us> wrote:
> > [copy off list, because the sourceware system admins throws temper tantrums]
> >> -----Original Message-----
> >> From: Dave L
> >> Sent: Wednesday, December 03, 2014 15:30
> >>
> >> ...but the git from github.com works fine.
> >>
> >> I installed Cygwin's version of git, and get this:
> >>
> >>     $ git clone https://github.com/nerdfever/pic32mx-bmf
> >>     Cloning into 'pic32mx-bmf'...
> >>     remote: Counting objects: 12, done.
> >>     remote: Total 12 (delta 0), reused 0 (delta 0)
> >>     error: failed to read delta-pack base object
> >>     300bdeb2fd209d24afb865584da10b78aa8fefc4
> >>     fatal: unpack-objects failed
> >
> > What file system are you on? Local NTFS or remote?
> 
> Aha - you're right.
> 
> It works fine on a local NTFS volume.
> 
> I get the error when I do it on Z:, which is mapped to a network drive
> (on another Windows box).

It works fine for me on a network drive mounted from another Windows
machine used via the cygdrive prefix:

  $ mount | grep cygdrive/z
  Z: on /cygdrive/z type ntfs (binary,posix=0,user,noumount,auto)
  $ cd /cygdrive/z
  $ git clone https://github.com/nerdfever/pic32mx-bmf
  Cloning into 'pic32mx-bmf'...
  remote: Counting objects: 12, done.
  remote: Total 12 (delta 0), reused 0 (delta 0)
  Unpacking objects: 100% (12/12), done.
  Checking connectivity... done.

I tried with two different mount points, one to a Cygwin-created remote
dir, one to a Windows-created remote dir.

> Is there a workaround? Why does this happen?

No idea.  How do you mount the drive, e.g., what does `mount' print for
the drive?  Or could this be a permission problem?  If all else fails
you could try to find out what happens via strace.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: [cygwin] Cygwin's git says "error: failed to read delta-pack base object"

[Dave Lindbergh]

On Wed, Dec 3, 2014 at 3:42 PM, Jason Pyeron <jpyeron@pdinc.us> wrote:
> [copy off list, because the sourceware system admins throws temper tantrums]
>> -----Original Message-----
>> From: Dave L
>> Sent: Wednesday, December 03, 2014 15:30
>>
>> ...but the git from github.com works fine.
>>
>> I installed Cygwin's version of git, and get this:
>>
>>     $ git clone https://github.com/nerdfever/pic32mx-bmf
>>     Cloning into 'pic32mx-bmf'...
>>     remote: Counting objects: 12, done.
>>     remote: Total 12 (delta 0), reused 0 (delta 0)
>>     error: failed to read delta-pack base object
>>     300bdeb2fd209d24afb865584da10b78aa8fefc4
>>     fatal: unpack-objects failed
>
> What file system are you on? Local NTFS or remote?

Aha - you're right.

It works fine on a local NTFS volume.

I get the error when I do it on Z:, which is mapped to a network drive
(on another Windows box).

Is there a workaround? Why does this happen?

--Dave

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple