Skip to main content
Start a Conversation

Unsolved

This post is more than 5 years old

apri_671533

1 Message

489

August 8th, 2008 02:00

File size still same as original size

Hi All,

I'm using new DX ver.6.20.090(SP1) Patch 01 on Windows 2003 Server SP2
Running on VMWare ESX

I wonder why when I dump some files on extended drive & purge all files, the size on it still same as original files.
Regarding from Admin Guide, after files being purged, files will be shorcut and 'shrink' in KB size. So some space will be freed
However, archive and 'shorcut' marked on files is no problem

Is anyone have same experience? Please advise...

Thanks,
Apriadi

DCCU

8 Posts

December 31st, 2008 06:00

The only way you can tell that it's freeing up space is to look at the total Free Space on the drive. You can tell which files are purged by the icon, it changes to an icon that looks like it has a tiny little clock on the bottom left of the icon.

coreylow

41 Posts

December 31st, 2008 15:00

the actual size of stub/tag is 4 Kb. But shows the same size as that of actual size so that it does not confuse the users.
This is because we use the Mircosoft offline attributes for offline files.

If you would like to check the size of each purge files (offline file), you can run NTFSinfo on the Extended Drive. (technet.microsoft.com/en-us/sysinternals/bb897424.aspx). It can be used to view information about the drive, including the allocation unit size. The tag size pre-6.3 will be the size of the allocation unit + 1kb.


DX Shell properties and Windows Explorer properties will show the ACTUAL size of the files. The way we identify the file is a file tags is using Microsoft Offline Attribute and the little black clock located at the bottom left of the icon.

Was this post helpful?

View All

No Events found!

Top