On Wed, Jul 7, 2010 at 6:04 AM, Christopher Faylor
wrote:
> On Wed, Jul 07, 2010 at 05:56:30AM -0700, Slide wrote:
>>
>>
>>> Thanks for your help. ?This problem should be fixed now in CVS.
>>> I switched off the entire mechanism which tries to resolve sharing
>>> violations for netapp drives.
>>>
On Wed, Jul 07, 2010 at 05:56:30AM -0700, Slide wrote:
>
>
>> Thanks for your help. ?This problem should be fixed now in CVS.
>> I switched off the entire mechanism which tries to resolve sharing
>> violations for netapp drives.
>>
>> What happens is this:
>>
>> The netapp drive is thoroughly confu
> Thanks for your help. This problem should be fixed now in CVS.
> I switched off the entire mechanism which tries to resolve sharing
> violations for netapp drives.
>
> What happens is this:
>
> The netapp drive is thoroughly confused when trying to move-and-delete
> a file or directory using a
On Jul 6 06:41, Slide wrote:
> On Tue, Jul 6, 2010 at 1:02 AM, Corinna Vinschen
> wrote:
> > On Jul 5 23:00, Slide wrote:
> >>
> >>
> >> > This funtionality wasn't available in 1.5, so, yes, this would only
> >> > have started with 1.7.
> >> >
> >> > So it seems that these netapp drives somehow
On Tue, Jul 6, 2010 at 1:02 AM, Corinna Vinschen
wrote:
> On Jul 5 23:00, Slide wrote:
>>
>>
>> > This funtionality wasn't available in 1.5, so, yes, this would only
>> > have started with 1.7.
>> >
>> > So it seems that these netapp drives somehow don't understand the
>> > entirely normal FileD
On Jul 5 23:00, Slide wrote:
>
>
> > This funtionality wasn't available in 1.5, so, yes, this would only
> > have started with 1.7.
> >
> > So it seems that these netapp drives somehow don't understand the
> > entirely normal FileDispositionInformation method, or they ignore it for
> > some unkn
> This funtionality wasn't available in 1.5, so, yes, this would only
> have started with 1.7.
>
> So it seems that these netapp drives somehow don't understand the
> entirely normal FileDispositionInformation method, or they ignore it for
> some unknown reason.
>
> Unfortunately the strace from
On Jul 2 08:11, Slide wrote:
>
>
> >
> > So, IIUC, youre'saying that the directories get renamed to this
> > temporary name, but they never disappear after rm -rf? Are you
> > sure that no other process is accessing them?
> >
> > Does Cygwin recognize the drive as netapp if you add a mount poin
>
> So, IIUC, youre'saying that the directories get renamed to this
> temporary name, but they never disappear after rm -rf? Are you
> sure that no other process is accessing them?
>
> Does Cygwin recognize the drive as netapp if you add a mount point for
> it? How to check: If the drive has b
On Jul 1 20:03, Slide wrote:
> On Thu, Jul 1, 2010 at 3:26 PM, Larry Hall (Cygwin)
> wrote:
> > On 7/1/2010 5:52 PM, Slide wrote:
> >
> >
> >
> >> What sort of information would you need for the share? I believe it is
> >> actually a Linux box running Samba for the share. I would have to
> >> do
On Jul 2 15:28, Corinna Vinschen wrote:
> On Jul 1 15:28, Eric Blake wrote:
> > On 07/01/2010 03:24 PM, Slide wrote:
> > > I am seeing a VERY odd problem. If I run "/usr/bin/rm -rf
> > > //computer/share/path/to/dir" to remove a directory on a network
> > > share. I get some directories created w
On Jul 1 15:28, Eric Blake wrote:
> On 07/01/2010 03:24 PM, Slide wrote:
> > I am seeing a VERY odd problem. If I run "/usr/bin/rm -rf
> > //computer/share/path/to/dir" to remove a directory on a network
> > share. I get some directories created with names like
> > .XXXf8a0015e3b00c65f07a9f20c
On Thu, Jul 1, 2010 at 3:26 PM, Larry Hall (Cygwin)
wrote:
> On 7/1/2010 5:52 PM, Slide wrote:
>
>
>
>> What sort of information would you need for the share? I believe it is
>> actually a Linux box running Samba for the share. I would have to
>> double check with my IT department on that. I shou
On 7/1/2010 5:52 PM, Slide wrote:
What sort of information would you need for the share? I believe it is
actually a Linux box running Samba for the share. I would have to
double check with my IT department on that. I should be able to get
any information needed about the share to help workarou
On Thu, Jul 1, 2010 at 2:28 PM, Eric Blake wrote:
> On 07/01/2010 03:24 PM, Slide wrote:
>> I am seeing a VERY odd problem. If I run "/usr/bin/rm -rf
>> //computer/share/path/to/dir" to remove a directory on a network
>> share. I get some directories created with names like
>> .XXXf8a0015e3b00
On 07/01/2010 03:24 PM, Slide wrote:
> I am seeing a VERY odd problem. If I run "/usr/bin/rm -rf
> //computer/share/path/to/dir" to remove a directory on a network
> share. I get some directories created with names like
> .XXXf8a0015e3b00c65f07a9f20c7a31 at the ROOT of the share (where
> XXX is
I am seeing a VERY odd problem. If I run "/usr/bin/rm -rf
//computer/share/path/to/dir" to remove a directory on a network
share. I get some directories created with names like
.XXXf8a0015e3b00c65f07a9f20c7a31 at the ROOT of the share (where
XXX is unprintable character with the value 0x3f). I
17 matches
Mail list logo
