Moving large files, delayed write error in XP Pro SP2
-
I've got a file that is 66 GB. (it is a virtual box VDI file) I want to move it from the drive I created it on, to another drive (with 70+ GB available). Always, after copying between 55 to 62 GB (NOT near 2^N), it fails with a "Delayed Write Failed" error. The target drive is set to write through the cache. I can still see the drive through other means, so it is not dead. I have run diagnostics, and the drive does not own up to any problems. I have tried copying it with explorer. I have written a program that copies, reading, writing and flushing a meg at a time. Always the same result I zipped it, and copied it to another machine, and tried to unzip it. (Its about 8 GB compressed) When unzipping, it writes around 60 - 62 GB into the target, and starts having delayed write failed error. So now we are on a totally different system, and it is generating the same type of error at roughly the same file size, on three different disks. I have also tried unzipping it on a W2K3 machine, and that went fine. Now I am trying to push it from the W2K3 machine to the XP Pro machine. NTFS is supposed to handle files with more bytes than there are grains of sand (give or take 15 :-D ) Is there some limit with XP on how big a single write session can be, or some other limit I might be hitting? TIA Richard
Silver member by constant and unflinching longevity.
-
I've got a file that is 66 GB. (it is a virtual box VDI file) I want to move it from the drive I created it on, to another drive (with 70+ GB available). Always, after copying between 55 to 62 GB (NOT near 2^N), it fails with a "Delayed Write Failed" error. The target drive is set to write through the cache. I can still see the drive through other means, so it is not dead. I have run diagnostics, and the drive does not own up to any problems. I have tried copying it with explorer. I have written a program that copies, reading, writing and flushing a meg at a time. Always the same result I zipped it, and copied it to another machine, and tried to unzip it. (Its about 8 GB compressed) When unzipping, it writes around 60 - 62 GB into the target, and starts having delayed write failed error. So now we are on a totally different system, and it is generating the same type of error at roughly the same file size, on three different disks. I have also tried unzipping it on a W2K3 machine, and that went fine. Now I am trying to push it from the W2K3 machine to the XP Pro machine. NTFS is supposed to handle files with more bytes than there are grains of sand (give or take 15 :-D ) Is there some limit with XP on how big a single write session can be, or some other limit I might be hitting? TIA Richard
Silver member by constant and unflinching longevity.
RichardM1 wrote:
Is there some limit with XP on how big a single write session can be, or some other limit I might be hitting?
http://support.microsoft.com/kb/330174[^] also read http://searchwinit.techtarget.com/tip/0,289483,sid1_gci1041334,00.html[^]
-
I've got a file that is 66 GB. (it is a virtual box VDI file) I want to move it from the drive I created it on, to another drive (with 70+ GB available). Always, after copying between 55 to 62 GB (NOT near 2^N), it fails with a "Delayed Write Failed" error. The target drive is set to write through the cache. I can still see the drive through other means, so it is not dead. I have run diagnostics, and the drive does not own up to any problems. I have tried copying it with explorer. I have written a program that copies, reading, writing and flushing a meg at a time. Always the same result I zipped it, and copied it to another machine, and tried to unzip it. (Its about 8 GB compressed) When unzipping, it writes around 60 - 62 GB into the target, and starts having delayed write failed error. So now we are on a totally different system, and it is generating the same type of error at roughly the same file size, on three different disks. I have also tried unzipping it on a W2K3 machine, and that went fine. Now I am trying to push it from the W2K3 machine to the XP Pro machine. NTFS is supposed to handle files with more bytes than there are grains of sand (give or take 15 :-D ) Is there some limit with XP on how big a single write session can be, or some other limit I might be hitting? TIA Richard
Silver member by constant and unflinching longevity.
-
I've got a file that is 66 GB. (it is a virtual box VDI file) I want to move it from the drive I created it on, to another drive (with 70+ GB available). Always, after copying between 55 to 62 GB (NOT near 2^N), it fails with a "Delayed Write Failed" error. The target drive is set to write through the cache. I can still see the drive through other means, so it is not dead. I have run diagnostics, and the drive does not own up to any problems. I have tried copying it with explorer. I have written a program that copies, reading, writing and flushing a meg at a time. Always the same result I zipped it, and copied it to another machine, and tried to unzip it. (Its about 8 GB compressed) When unzipping, it writes around 60 - 62 GB into the target, and starts having delayed write failed error. So now we are on a totally different system, and it is generating the same type of error at roughly the same file size, on three different disks. I have also tried unzipping it on a W2K3 machine, and that went fine. Now I am trying to push it from the W2K3 machine to the XP Pro machine. NTFS is supposed to handle files with more bytes than there are grains of sand (give or take 15 :-D ) Is there some limit with XP on how big a single write session can be, or some other limit I might be hitting? TIA Richard
Silver member by constant and unflinching longevity.
Delayed write errors simply mean write errors that occurred when the system tried to write back from cache to the disk. The system caches writes in order to consolidate them, to maximise writing performance, and to support fast reads back from recently-written locations. The problem is with the disk hardware, not the OS.
"Multithreading is just one damn thing after, before, or simultaneous with another." - Andrei Alexandrescu
-
Delayed write errors simply mean write errors that occurred when the system tried to write back from cache to the disk. The system caches writes in order to consolidate them, to maximise writing performance, and to support fast reads back from recently-written locations. The problem is with the disk hardware, not the OS.
"Multithreading is just one damn thing after, before, or simultaneous with another." - Andrei Alexandrescu
Normally I would agree with you - but I have tried it on multiple hard disks, XP chokes on all of them. I have run full diagnostics on the disks, and there are no problems with them. SMART thinks they have no issues, as well. This is something intrinsic to XP, not the drives.
Silver member by constant and unflinching longevity.
-
Normally I would agree with you - but I have tried it on multiple hard disks, XP chokes on all of them. I have run full diagnostics on the disks, and there are no problems with them. SMART thinks they have no issues, as well. This is something intrinsic to XP, not the drives.
Silver member by constant and unflinching longevity.
This is something specific to your machine/Windows installation. I've written some tests creating and copying 80GB files between drives without any issues.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008 -
This is something specific to your machine/Windows installation. I've written some tests creating and copying 80GB files between drives without any issues.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008 -
I could see that, but they are plain vanilla XP Pro SP2 installs. One on a Dell, and one on a ThinkPad. Both act the same. Win 2K3 does not.
Silver member by constant and unflinching longevity.
Do you have some anti-virus/anti-spyware software or some disk management tools, like Diskeeper, installed on these machines?
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008 -
Do you have some anti-virus/anti-spyware software or some disk management tools, like Diskeeper, installed on these machines?
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008Dave, Thank you. Stupid me, of course if there is an apparent OS issue, I should have checked at least anti virus first. I must not be thinking straight to have missed checking that. :sigh: I have SmartDefrag running on both the XP machines, but not the 2k3 machine, and symantec endpoint on the thinkpad. I'll turn all them off and try again. Richard
Silver member by constant and unflinching longevity.