Posted by Eddie on November 19, 2009, 4:46 pmPlease Register and login to reply and use other advanced options
I use Windows XP and I have these partitions:
C contains the XP system.
D contains data
E is empty
I usually need to copy approx 10GB from D to E. I want the data to
be stored on E as unfragmented as possible.
Would running an application on C at the same time somehow mess up
the copy of data from D to E in such a way as to make the data on E
more fragmented?
(Maybe affecting the numbers of simultaneous "streams" of data or
maybe affecting the buffers being used or something like that.)
Posted by Sjouke Burry on November 19, 2009, 6:18 pm
Eddie wrote:
> I use Windows XP and I have these partitions:
>
> C contains the XP system.
> D contains data
> E is empty
>
> I usually need to copy approx 10GB from D to E. I want the data to
> be stored on E as unfragmented as possible.
>
> Would running an application on C at the same time somehow mess up
> the copy of data from D to E in such a way as to make the data on E
> more fragmented?
>
> (Maybe affecting the numbers of simultaneous "streams" of data or
> maybe affecting the buffers being used or something like that.)
>
Fragmenting on E only occurs when more programs try to write to it
at the same time, so only when the C program tries to write E at the
same time, will fragmentation take place.
The time slicing between you and the C progam in itself will not
cause fragmentation.
Posted by detlev.e on November 24, 2009, 2:55 am
Sjouke Burry schrieb:
> Fragmenting on E only occurs when more programs try to write to it
> at the same time, so only when the C program tries to write E at the
> same time, will fragmentation take place.
> The time slicing between you and the C progam in itself will not
> cause fragmentation.
Doesn't the OS write systemv olume information to that partition and
perhaps it des that whilst copying data from one partition to another?
Posted by Rod Speed on November 24, 2009, 4:04 am
detlev.e wrote
> Sjouke Burry wrote
>> Fragmenting on E only occurs when more programs try to write to it
>> at the same time, so only when the C program tries to write E at the
>> same time, will fragmentation take place.
>> The time slicing between you and the C progam in itself will not
>> cause fragmentation.
> Doesn't the OS write system volume information to that partition
Yes.
> and perhaps it des that whilst copying data from one partition to another?
Nope, nothing gets written to any partition that isnt being copied to.
And that 'system volume information' doesnt affect fragmentation of files on
that volume anyway.
Posted by kony on November 24, 2009, 2:07 pm
On Tue, 24 Nov 2009 08:55:22 +0100, "detlev.e"
>Sjouke Burry schrieb:
>> Fragmenting on E only occurs when more programs try to write to it
>> at the same time, so only when the C program tries to write E at the
>> same time, will fragmentation take place.
>> The time slicing between you and the C progam in itself will not
>> cause fragmentation.
>Doesn't the OS write systemv olume information to that partition and
>perhaps it des that whilst copying data from one partition to another?
It would only be a matter of discountinous writes, that it
seeks between writing each volume. It still picks up at the
next contiguous block of free space.
>
> C contains the XP system.
> D contains data
> E is empty
>
> I usually need to copy approx 10GB from D to E. I want the data to
> be stored on E as unfragmented as possible.
>
> Would running an application on C at the same time somehow mess up
> the copy of data from D to E in such a way as to make the data on E
> more fragmented?
>
> (Maybe affecting the numbers of simultaneous "streams" of data or
> maybe affecting the buffers being used or something like that.)
>