Re: 5308-64: Serious file I/O issue?

  • Thread starter Prashanth Prahalad [MSFT]
  • Start date
P

Prashanth Prahalad [MSFT]

I'm not sure about the exact nature of the problem you are seeing while
transferring large files. If you are still seeing problems and can elaborate
on the problem, we could diagonise the issue.

* Is transfer failing with any particular error code ?
* Is the system blue-screening while transferring data ?
* Is the system taking a unusually long time to tranfer fails (which might
manifest itself as a system lock/hang) ?

Also, what OS are the server and client running ?

If you can get a network capture (using netmon/ethereal), that might be a
good start to investigate this.

Thanks ~
Prashanth

Vista Remote File Systems


"Vista Tester" <[email protected]> wrote in message
news:[email protected]
> I'm finding serious problems (system lock/crash) trying to xfer files from
> a shared folder across a network. So far, it only seems to be a problem
> in the 64-bit version of Vista.
>
> Try placing a 50MB file in the Public folder on a 64bit system. Make sure
> sharing is turned on. Then, go to another machine and try to copy the
> file through the network. If that works, then try it with a 1G file.
>
> There are a LOT of variables here, so before I spend much more time trying
> to diagnose, I wanted to find out if others had noticed any issues.
>
 

My Computer

V

Vista Tester

Here's some more detail:

1) The same problem occurs when running under safe mode wi networking
2) I'm mapping a network drive to the remote computer (drive S:)
3) I copy the file from my 5308-64 machine to drive S (XP-pro machine)
4) "Calculating time remaining" box pops up - and never gets to next step
5) The network connection drops (?!) Drive S no longer exists
6) There doesn't seem to be a corresponding error message in the log,
nor is there an error message on screen
7) The only way to recover is to power the machine off

The error sounds real familiar. I seem to remember something about the
drive mappings disappearing during file copies back in Win 98. I dunno if
it's related...

"Prashanth Prahalad [MSFT]" <[email protected]> wrote in message
news:[email protected]
>
> I'm not sure about the exact nature of the problem you are seeing while
> transferring large files. If you are still seeing problems and can
> elaborate on the problem, we could diagonise the issue.
>
> * Is transfer failing with any particular error code ?
> * Is the system blue-screening while transferring data ?
> * Is the system taking a unusually long time to tranfer fails (which might
> manifest itself as a system lock/hang) ?
>
> Also, what OS are the server and client running ?
>
> If you can get a network capture (using netmon/ethereal), that might be a
> good start to investigate this.
>
> Thanks ~
> Prashanth
>
> Vista Remote File Systems
>
>
> "Vista Tester" <[email protected]> wrote in message
> news:[email protected]
>> I'm finding serious problems (system lock/crash) trying to xfer files
>> from a shared folder across a network. So far, it only seems to be a
>> problem in the 64-bit version of Vista.
>>
>> Try placing a 50MB file in the Public folder on a 64bit system. Make
>> sure sharing is turned on. Then, go to another machine and try to copy
>> the file through the network. If that works, then try it with a 1G file.
>>
>> There are a LOT of variables here, so before I spend much more time
>> trying to diagnose, I wanted to find out if others had noticed any
>> issues.
>>

>
>
 

My Computer

P

Patrick Elliott [MVP]

Sorry for the long delay, are you still having this problem?

--
Patrick Elliott [MVP]
Windows Server System - File/Storage
http://www.msblog.org
CFS team blog: http://blogs.technet.com/filecab

"Vista Tester" <[email protected]> wrote in message
news:[email protected]
> Here's some more detail:
>
> 1) The same problem occurs when running under safe mode wi networking
> 2) I'm mapping a network drive to the remote computer (drive S:)
> 3) I copy the file from my 5308-64 machine to drive S (XP-pro machine)
> 4) "Calculating time remaining" box pops up - and never gets to next step
> 5) The network connection drops (?!) Drive S no longer exists
> 6) There doesn't seem to be a corresponding error message in the log,
> nor is there an error message on screen
> 7) The only way to recover is to power the machine off
>
> The error sounds real familiar. I seem to remember something about the
> drive mappings disappearing during file copies back in Win 98. I dunno if
> it's related...
>
> "Prashanth Prahalad [MSFT]" <[email protected]> wrote in message
> news:[email protected]
>>
>> I'm not sure about the exact nature of the problem you are seeing while
>> transferring large files. If you are still seeing problems and can
>> elaborate on the problem, we could diagonise the issue.
>>
>> * Is transfer failing with any particular error code ?
>> * Is the system blue-screening while transferring data ?
>> * Is the system taking a unusually long time to tranfer fails (which
>> might manifest itself as a system lock/hang) ?
>>
>> Also, what OS are the server and client running ?
>>
>> If you can get a network capture (using netmon/ethereal), that might be a
>> good start to investigate this.
>>
>> Thanks ~
>> Prashanth
>>
>> Vista Remote File Systems
>>
>>
>> "Vista Tester" <[email protected]> wrote in message
>> news:[email protected]
>>> I'm finding serious problems (system lock/crash) trying to xfer files
>>> from a shared folder across a network. So far, it only seems to be a
>>> problem in the 64-bit version of Vista.
>>>
>>> Try placing a 50MB file in the Public folder on a 64bit system. Make
>>> sure sharing is turned on. Then, go to another machine and try to copy
>>> the file through the network. If that works, then try it with a 1G
>>> file.
>>>
>>> There are a LOT of variables here, so before I spend much more time
>>> trying to diagnose, I wanted to find out if others had noticed any
>>> issues.
>>>

>>
>>

>
 

My Computer

V

Vista Tester

Yup. I set things up to do a Kernel Dump on crash, but the mapped
drive/folder sharing lockup doesn't cause a managed crash. It just locks
the system solid.

Since I noted these issues, there has been at least one (or two?) interim
release of a new beta. Does it make sense to continue to debug an older
release when the code we might be addressing could have been changed?

"Patrick Elliott [MVP]" <[email protected]_mo_ve.gmailDOTcom> wrote in
message news:%[email protected]
> Sorry for the long delay, are you still having this problem?
>
> --
> Patrick Elliott [MVP]
> Windows Server System - File/Storage
> http://www.msblog.org
> CFS team blog: http://blogs.technet.com/filecab
>
> "Vista Tester" <[email protected]> wrote in message
> news:[email protected]
>> Here's some more detail:
>>
>> 1) The same problem occurs when running under safe mode wi networking
>> 2) I'm mapping a network drive to the remote computer (drive S:)
>> 3) I copy the file from my 5308-64 machine to drive S (XP-pro machine)
>> 4) "Calculating time remaining" box pops up - and never gets to next step
>> 5) The network connection drops (?!) Drive S no longer exists
>> 6) There doesn't seem to be a corresponding error message in the log,
>> nor is there an error message on screen
>> 7) The only way to recover is to power the machine off
>>
>> The error sounds real familiar. I seem to remember something about the
>> drive mappings disappearing during file copies back in Win 98. I dunno
>> if it's related...
>>
>> "Prashanth Prahalad [MSFT]" <[email protected]> wrote in
>> message news:[email protected]
>>>
>>> I'm not sure about the exact nature of the problem you are seeing while
>>> transferring large files. If you are still seeing problems and can
>>> elaborate on the problem, we could diagonise the issue.
>>>
>>> * Is transfer failing with any particular error code ?
>>> * Is the system blue-screening while transferring data ?
>>> * Is the system taking a unusually long time to tranfer fails (which
>>> might manifest itself as a system lock/hang) ?
>>>
>>> Also, what OS are the server and client running ?
>>>
>>> If you can get a network capture (using netmon/ethereal), that might be
>>> a good start to investigate this.
>>>
>>> Thanks ~
>>> Prashanth
>>>
>>> Vista Remote File Systems
>>>
>>>
>>> "Vista Tester" <[email protected]> wrote in message
>>> news:[email protected]
>>>> I'm finding serious problems (system lock/crash) trying to xfer files
>>>> from a shared folder across a network. So far, it only seems to be a
>>>> problem in the 64-bit version of Vista.
>>>>
>>>> Try placing a 50MB file in the Public folder on a 64bit system. Make
>>>> sure sharing is turned on. Then, go to another machine and try to copy
>>>> the file through the network. If that works, then try it with a 1G
>>>> file.
>>>>
>>>> There are a LOT of variables here, so before I spend much more time
>>>> trying to diagnose, I wanted to find out if others had noticed any
>>>> issues.
>>>>
>>>
>>>

>>

>
>
 

My Computer

A

Andre Da Costa [Extended64]

You are on dead code, this is likely to be fixed in the most recently
available build. In your case, I would try BETA 2 when it becomes Public.
--
--
Andre
Windows Connected | http://www.windowsconnected.com
Extended64 | http://www.extended64.com
Blog | http://www.extended64.com/blogs/andre
http://spaces.msn.com/members/adacosta

"Vista Tester" <[email protected]> wrote in message
news:[email protected]
> Yup. I set things up to do a Kernel Dump on crash, but the mapped
> drive/folder sharing lockup doesn't cause a managed crash. It just locks
> the system solid.
>
> Since I noted these issues, there has been at least one (or two?) interim
> release of a new beta. Does it make sense to continue to debug an older
> release when the code we might be addressing could have been changed?
>
> "Patrick Elliott [MVP]" <[email protected]_mo_ve.gmailDOTcom> wrote in
> message news:%[email protected]
>> Sorry for the long delay, are you still having this problem?
>>
>> --
>> Patrick Elliott [MVP]
>> Windows Server System - File/Storage
>> http://www.msblog.org
>> CFS team blog: http://blogs.technet.com/filecab
>>
>> "Vista Tester" <[email protected]> wrote in message
>> news:[email protected]
>>> Here's some more detail:
>>>
>>> 1) The same problem occurs when running under safe mode wi networking
>>> 2) I'm mapping a network drive to the remote computer (drive S:)
>>> 3) I copy the file from my 5308-64 machine to drive S (XP-pro machine)
>>> 4) "Calculating time remaining" box pops up - and never gets to next
>>> step
>>> 5) The network connection drops (?!) Drive S no longer exists
>>> 6) There doesn't seem to be a corresponding error message in the log,
>>> nor is there an error message on screen
>>> 7) The only way to recover is to power the machine off
>>>
>>> The error sounds real familiar. I seem to remember something about the
>>> drive mappings disappearing during file copies back in Win 98. I dunno
>>> if it's related...
>>>
>>> "Prashanth Prahalad [MSFT]" <[email protected]> wrote in
>>> message news:[email protected]
>>>>
>>>> I'm not sure about the exact nature of the problem you are seeing while
>>>> transferring large files. If you are still seeing problems and can
>>>> elaborate on the problem, we could diagonise the issue.
>>>>
>>>> * Is transfer failing with any particular error code ?
>>>> * Is the system blue-screening while transferring data ?
>>>> * Is the system taking a unusually long time to tranfer fails (which
>>>> might manifest itself as a system lock/hang) ?
>>>>
>>>> Also, what OS are the server and client running ?
>>>>
>>>> If you can get a network capture (using netmon/ethereal), that might be
>>>> a good start to investigate this.
>>>>
>>>> Thanks ~
>>>> Prashanth
>>>>
>>>> Vista Remote File Systems
>>>>
>>>>
>>>> "Vista Tester" <[email protected]> wrote in message
>>>> news:[email protected]
>>>>> I'm finding serious problems (system lock/crash) trying to xfer files
>>>>> from a shared folder across a network. So far, it only seems to be a
>>>>> problem in the 64-bit version of Vista.
>>>>>
>>>>> Try placing a 50MB file in the Public folder on a 64bit system. Make
>>>>> sure sharing is turned on. Then, go to another machine and try to
>>>>> copy the file through the network. If that works, then try it with a
>>>>> 1G file.
>>>>>
>>>>> There are a LOT of variables here, so before I spend much more time
>>>>> trying to diagnose, I wanted to find out if others had noticed any
>>>>> issues.
>>>>>
>>>>
>>>>
>>>

>>
>>

>
 

My Computer

Top