odd behavior of "dir"

  • This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.
Oct 31, 2012
1
0
#1
In the interest of saving disk space, I've activated deduplication on my ntfs-formatted drives with Windows 8 (with the powershell's "Enable-DedupVolume" command) and it has definately had a positive effect for my previously-near-full hard drives.

However, I like take command and unforunately now, running a simple "dir" gives me all sort of wierdness. Here's a sample listing:

[C:\Program Files\JPSoft\TCMD14x64]dir "m:\Virtual Machines\New folder"

Volume in drive M is 2T6 Serial number is cce3:2649
Directory of M:\Virtual Machines\New folder\*

10/21/2012 3:04 <DIR> .
10/21/2012 3:04 <DIR> ..
10/21/2012 3:04 <DIR> Other 64-bit.vmx.lck
9/09/2012 15:12 <SYMLINK> Other 64-bit-s001.vmdk [M:\Virtual Machines\N
ew folder\Other 64-bit-s001.vmdk]
9/09/2012 15:12 <SYMLINK> Other 64-bit-s002.vmdk [M:\Virtual Machines\N
ew folder\Other 64-bit-s002.vmdk]
9/09/2012 15:12 <SYMLINK> Other 64-bit-s003.vmdk [M:\Virtual Machines\N
ew folder\Other 64-bit-s003.vmdk]
9/09/2012 15:12 <SYMLINK> Other 64-bit-s004.vmdk [M:\Virtual Machines\N
ew folder\Other 64-bit-s004.vmdk]
9/09/2012 15:12 <SYMLINK> Other 64-bit-s005.vmdk [M:\Virtual Machines\N
ew folder\Other 64-bit-s005.vmdk]
9/09/2012 15:12 <SYMLINK> Other 64-bit-s006.vmdk [M:\Virtual Machines\N
ew folder\Other 64-bit-s006.vmdk]
9/09/2012 15:12 <SYMLINK> Other 64-bit-s007.vmdk [M:\Virtual Machines\N
ew folder\Other 64-bit-s007.vmdk]
9/09/2012 15:12 <SYMLINK> Other 64-bit-s008.vmdk [M:\Virtual Machines\N
ew folder\Other 64-bit-s008.vmdk]
9/09/2012 15:12 <SYMLINK> Other 64-bit-s009.vmdk [M:\Virtual Machines\N
ew folder\Other 64-bit-s009.vmdk]
9/09/2012 15:12 <SYMLINK> Other 64-bit-s010.vmdk [M:\Virtual Machines\N
ew folder\Other 64-bit-s010.vmdk]
9/09/2012 15:12 <SYMLINK> Other 64-bit-s011.vmdk [M:\Virtual Machines\N
ew folder\Other 64-bit-s011.vmdk]
9/09/2012 15:12 8,684 Other 64-bit.nvram
9/09/2012 15:07 920 Other 64-bit.vmdk
9/09/2012 15:07 0 Other 64-bit.vmsd
9/09/2012 15:12 2,135 Other 64-bit.vmx
9/09/2012 15:07 267 Other 64-bit.vmxf
9/09/2012 15:09 <SYMLINK> vmware-0.log [M:\Virtual Machines\New folder\
vmware-0.log]
9/09/2012 15:12 <SYMLINK> vmware.log [M:\Virtual Machines\New folder\vm
ware.log]
3,771,367 bytes in 18 files and 3 dirs 3,788,800 bytes allocated

whereas the output of cmd.exe is:

C:\Users\ctimm_000>dir "m:\Virtual Machines\New folder"
Volume in drive M is 2T6
Volume Serial Number is CCE3-2649

Directory of m:\Virtual Machines\New folder

10/21/2012 03:04 AM <DIR> .
10/21/2012 03:04 AM <DIR> ..
09/09/2012 03:12 PM 327,680 Other 64-bit-s001.vmdk
09/09/2012 03:12 PM 327,680 Other 64-bit-s002.vmdk
09/09/2012 03:12 PM 327,680 Other 64-bit-s003.vmdk
09/09/2012 03:12 PM 327,680 Other 64-bit-s004.vmdk
09/09/2012 03:12 PM 327,680 Other 64-bit-s005.vmdk
09/09/2012 03:12 PM 327,680 Other 64-bit-s006.vmdk
09/09/2012 03:12 PM 327,680 Other 64-bit-s007.vmdk
09/09/2012 03:12 PM 327,680 Other 64-bit-s008.vmdk
09/09/2012 03:12 PM 327,680 Other 64-bit-s009.vmdk
09/09/2012 03:12 PM 327,680 Other 64-bit-s010.vmdk
09/09/2012 03:12 PM 65,536 Other 64-bit-s011.vmdk
09/09/2012 03:12 PM 8,684 Other 64-bit.nvram
09/09/2012 03:07 PM 920 Other 64-bit.vmdk
09/09/2012 03:07 PM 0 Other 64-bit.vmsd
09/09/2012 03:12 PM 2,135 Other 64-bit.vmx
10/21/2012 03:04 AM <DIR> Other 64-bit.vmx.lck
09/09/2012 03:07 PM 267 Other 64-bit.vmxf
09/09/2012 03:09 PM 207,289 vmware-0.log
09/09/2012 03:12 PM 209,736 vmware.log
18 File(s) 3,771,367 bytes

(the output of powershell is also correct.)

Apparently take command thinks my folder is just full of symlinks except for a few files which were presumably too small to dedup.