T
Tom Scales
I have a machine that is running Vista Business.
The machine has an external eSata Raid5 drive, running off a Silicon Image
3132 controller. The controller has proper Vista drivers. The enclosure is
a Silverstone DS351 (a very nice Home theater Raid box).
The drive is large (3TB), so it is a GDT drive (which is why I was forced to
Vista, since XP doesn't support a drive over 2TB).
Here's the problem.
Quite often (but not always), when I move a file from this drive to another
drive (a network share), the file copies to the network share properly, but
the entry still shows up in Explorer on the 'old' Raid5 drive. When you try
to access the file, it says it is in use (when it is really gone). This is
very, very annoying. Only a reboot makes the files go away.
I have searched this newsgroup and google'd to death, but can't fine this
problem.
Indexing is turned OFF for this drive as I find it completely and utterly
worthless and don't want the overhead.
It is not unique to the computer, as I have moved the controller and Raid5
drive to a different computer and the problem persists.
If it matters, the files are quite large (2GB+). This behavior does not
occur on any other drive.
Any thoughts and suggestions? It's annoying as heck.
Tom
The machine has an external eSata Raid5 drive, running off a Silicon Image
3132 controller. The controller has proper Vista drivers. The enclosure is
a Silverstone DS351 (a very nice Home theater Raid box).
The drive is large (3TB), so it is a GDT drive (which is why I was forced to
Vista, since XP doesn't support a drive over 2TB).
Here's the problem.
Quite often (but not always), when I move a file from this drive to another
drive (a network share), the file copies to the network share properly, but
the entry still shows up in Explorer on the 'old' Raid5 drive. When you try
to access the file, it says it is in use (when it is really gone). This is
very, very annoying. Only a reboot makes the files go away.
I have searched this newsgroup and google'd to death, but can't fine this
problem.
Indexing is turned OFF for this drive as I find it completely and utterly
worthless and don't want the overhead.
It is not unique to the computer, as I have moved the controller and Raid5
drive to a different computer and the problem persists.
If it matters, the files are quite large (2GB+). This behavior does not
occur on any other drive.
Any thoughts and suggestions? It's annoying as heck.
Tom