| Author |
Message |
Andrew Parker
Guest
|
 Posted:
Tue Sep 20, 2005 4:16 pm Post subject:
Delayed Write Failure |
|
|
I have an Iomega 400r NAS with WSS 2003 and multiple Windows XP Pro desktops.
Users in the same building as the NAS have no reported problems with saving
documents/files to the NAS. I do however have reports of users in another
building receiving Delayed Write Failure messages accompanied by an Event 50
in the event log being written. The link between the buildings is gigabit
fiber optic with HP managed switches. I have downloaded a hotfix from
Microsoft, but it said the file was already included with SP1.
Iomega told me that the prescribed way of using the NAS is to copy the file
from the NAS to your local machine, make your changes, then copy the file
back up to the server.
Any ideas? Any thoughts? |
|
| Back to top |
|
 |
Pat [MSFT]
Guest
|
| Posted:
Tue Sep 20, 2005 10:30 pm Post subject:
Re: Delayed Write Failure |
|
|
Delayed write failures means that the client is not receiving a confirmation
that the write succeeded in a timely fashion (not necessarily that the write
failed, just that we can't confirm that it succeeded). So, it could be a
latency or dropped packet issue. Since the issue appears to be isolated to
remote users I would start with a network analysis.
Pat
"Andrew Parker" <aparker@hyde.edu> wrote in message
news:4299B88E-E9AF-484E-BECF-7E53BBA369BC@microsoft.com...
| Quote: | I have an Iomega 400r NAS with WSS 2003 and multiple Windows XP Pro
desktops.
Users in the same building as the NAS have no reported problems with
saving
documents/files to the NAS. I do however have reports of users in another
building receiving Delayed Write Failure messages accompanied by an Event
50
in the event log being written. The link between the buildings is gigabit
fiber optic with HP managed switches. I have downloaded a hotfix from
Microsoft, but it said the file was already included with SP1.
Iomega told me that the prescribed way of using the NAS is to copy the
file
from the NAS to your local machine, make your changes, then copy the file
back up to the server.
Any ideas? Any thoughts?
|
|
|
| Back to top |
|
|
Andrew Parker
Guest
|
| Posted:
Tue Sep 20, 2005 10:45 pm Post subject:
Re: Delayed Write Failure |
|
|
OK. The other part of the puzzle, that I did not include before, is that i
had the same data on an older Dell PowerEdge server running Windows 2000
Server with the same network equipment and did not ever have this problem.
Does that change it any?
"Pat [MSFT]" wrote:
| Quote: | Delayed write failures means that the client is not receiving a confirmation
that the write succeeded in a timely fashion (not necessarily that the write
failed, just that we can't confirm that it succeeded). So, it could be a
latency or dropped packet issue. Since the issue appears to be isolated to
remote users I would start with a network analysis.
Pat
"Andrew Parker" <aparker@hyde.edu> wrote in message
news:4299B88E-E9AF-484E-BECF-7E53BBA369BC@microsoft.com...
I have an Iomega 400r NAS with WSS 2003 and multiple Windows XP Pro
desktops.
Users in the same building as the NAS have no reported problems with
saving
documents/files to the NAS. I do however have reports of users in another
building receiving Delayed Write Failure messages accompanied by an Event
50
in the event log being written. The link between the buildings is gigabit
fiber optic with HP managed switches. I have downloaded a hotfix from
Microsoft, but it said the file was already included with SP1.
Iomega told me that the prescribed way of using the NAS is to copy the
file
from the NAS to your local machine, make your changes, then copy the file
back up to the server.
Any ideas? Any thoughts?
|
|
|
| Back to top |
|
|
Pat [MSFT]
Guest
|
| Posted:
Wed Sep 21, 2005 10:50 pm Post subject:
Re: Delayed Write Failure |
|
|
Possibly, it just adds the networking gear in the NAS as a possible
candidate for the issue. You can also look at the perfmon counter: Logical
Disk:Sec/Write, which will tell you how long it takes for a write to
complete. If it is high, you can get those errors as well and will
exonerate the network.
Pat
"Andrew Parker" <aparker@hyde.edu> wrote in message
news:0030F141-B36D-4FB9-AF9E-09076BD62395@microsoft.com...
| Quote: | OK. The other part of the puzzle, that I did not include before, is that
i
had the same data on an older Dell PowerEdge server running Windows 2000
Server with the same network equipment and did not ever have this problem.
Does that change it any?
"Pat [MSFT]" wrote:
Delayed write failures means that the client is not receiving a
confirmation
that the write succeeded in a timely fashion (not necessarily that the
write
failed, just that we can't confirm that it succeeded). So, it could be a
latency or dropped packet issue. Since the issue appears to be isolated
to
remote users I would start with a network analysis.
Pat
"Andrew Parker" <aparker@hyde.edu> wrote in message
news:4299B88E-E9AF-484E-BECF-7E53BBA369BC@microsoft.com...
I have an Iomega 400r NAS with WSS 2003 and multiple Windows XP Pro
desktops.
Users in the same building as the NAS have no reported problems with
saving
documents/files to the NAS. I do however have reports of users in
another
building receiving Delayed Write Failure messages accompanied by an
Event
50
in the event log being written. The link between the buildings is
gigabit
fiber optic with HP managed switches. I have downloaded a hotfix from
Microsoft, but it said the file was already included with SP1.
Iomega told me that the prescribed way of using the NAS is to copy the
file
from the NAS to your local machine, make your changes, then copy the
file
back up to the server.
Any ideas? Any thoughts?
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in