'Used' space on a new partition?

  • Thread starter Thread starter Terry Pinnell
  • Start date Start date
T

Terry Pinnell

I made a new partition H on my third HD, large enough to contain a
copy of my XP OS from C. But when I came to use Drive Image to make
the copy, it said destination was too small. On inspection, I found
that although it was apparently EMPTY, it had a 'Used' figure of 122MB
- just enough to take it fractionally below the size of C.

Why would a brand new partition have *any* used space? The only
content I can see is a RECYCLER folder, but that's '35 bytes', and I
can't seem to remove it anyway.
 
Terry said:
I made a new partition H on my third HD, large enough to contain a
copy of my XP OS from C. But when I came to use Drive Image to make
the copy, it said destination was too small. On inspection, I found
that although it was apparently EMPTY, it had a 'Used' figure of 122MB
- just enough to take it fractionally below the size of C.

Why would a brand new partition have *any* used space? The only
content I can see is a RECYCLER folder, but that's '35 bytes', and I
can't seem to remove it anyway.
Click to expand...

Are you by any chance using the "Norton Protected Recycle Bin"? If so,
disable the service and restart the machine.
 
You are creating an image file? Of course there is file system overhead.

FAT32 has 0.1%, NTFS about 50 parts/million.
 
J. Clarke said:
Are you by any chance using the "Norton Protected Recycle Bin"? If so,
disable the service and restart the machine.
Click to expand...

Yes, thanks, I suspect that might have been the cause. I've moved on
in various ways since then (including laboriously enlarging the 12GB
partition to about 12.5GB to be on the sure side), so it's not
possible to be definitive now. But one step I did take was to ensure
recycling was not applied to that partition. Presumably space of 122MB
had been 'reserved' by Norton? But why then was the folder being shown
by WinXP as a mere 35 bytes?
 
Jim said:
Remove the partition you created. Try the copy in DI again.
Click to expand...

Thanks. I resized it a bit and that particular problem went away.

I now have other more serious ones! But will post separately under
'Why this configuration not working?'
 
Eric Gisin said:
You are creating an image file? Of course there is file system overhead.

FAT32 has 0.1%, NTFS about 50 parts/million.
Click to expand...

Not sure I follow. How is that relevant to my query? And anyway it was
a partition I created, not an image file. I then copied an OS from
another partition into it, using Drive Image > Copy Drive.
 
I thought you creating an image file. If you copy partitions, used space is ignored.

If you create multiple primary partitions of same size, the first will be 63/2 KB smaller.
This is due to the MBR track. The size diff does not show up in Disk Managers.
 
Back
Top