bug report

Matt Mackall mpm at selenic.com
Wed Dec 2 02:08:23 UTC 2009


On Tue, 2009-12-01 at 17:21 -0800, Fred Batty wrote:
> Matt Mackall wrote:
> > On Tue, 2009-12-01 at 16:44 -0800, Fred Batty wrote:
> >   
> >> Matt Mackall wrote:
> >>     
> >>> On Tue, 2009-12-01 at 16:07 -0800, Fred Batty wrote:
> >>>   
> >>>       
> >>>> Yes, and I can clone successfully if the filesystem is local.
> >>>>     
> >>>>         
> >>>   
> >>>       
> >>>> Matt Mackall wrote:
> >>>>     
> >>>>         
> >>>>> On Tue, 2009-12-01 at 16:01 -0800, Fred Batty wrote:
> >>>>>   
> >>>>>       
> >>>>>           
> >>>>>> I don't believe so. But like I said, checking out the workspace fresh on 
> >>>>>> the same filesystem also errors.
> >>>>>>         
> >>>>>>             
> >>>   
> >>>       
> >>>>>>     
> >>>>>>         
> >>>>>>             
> >>>>> Jargon fail. Are you saying you're cloning from a known-good source?
> >>>>>       
> >>>>>           
> >>> I'm afraid I can't reconcile these two statements. Let's try again.
> >>>
> >>> What I understand so far:
> >>>
> >>> - you've got a damaged repo
> >>> - you're using Cygwin under Virtualbox
> >>> - you're using CIFS to mount the filesystem from Win7 host
> >>>
> >>> What I'd like to know:
> >>>
> >>> - do you have a remote repo that passes verify?
> >>>   
> >>>       
> >> I don't have access to the remote repo. But I can successfully clone 
> >> from it writing to a local filesystem.
> >>     
> >
> >   
> >>> - what happens when you make a fresh clone from a known-good remote
> >>> source[1]?
> >>>   
> >>>       
> >> Writing to the disk from the Windows host, it fails with the zlib error.
> >>
> >> Writing to a local filesystem, it works.
> >>     
> >
> > Yeah, you already said that. And I still don't understand what you're
> > trying to tell me. I don't know what "disk from the Windows host" means
> > and how its different from "local filesystem". More clarity, please.
> >
> >   
> The disk from the Windows host machine is mounted in the VM using 
> Windows drive letter mapping as if both machines were on a LAN. The 
> local filesystem is on the VM's own (virtual) disk.

I see. Sounds like there's still some Virtualbox filesystem-related
brain damage happening here. Cloning on Windows/Samba shares is known to
work elsewhere.

-- 
http://selenic.com : development and support for Mercurial and Linux





More information about the Mercurial mailing list