


Sort-of works, but it only prints sizes on files, not directories. Windows admins haven’t been so lucky…at least those that wanted to do it on the command-line (which is becoming increasingly important as Microsoft focuses more on promoting Windows Server Core and PowerShell). This has been really easy for Linux admins for a long time now: Do thisĪnd delete folders or files from folders at the top that look like they want to be deleted. As usual, they have no idea why they’re running out of space, but they need you, the sysadmin, to fix it, and they need it done yesterday. So, at least for these ssd drives the parallel processing results in worthwhile speed-ups.A file share that a group in your business is dependent on is running out of space. > btw, I just ran robocopy with /mt:1, and it took around 42 seconds on the same drive, which is about what I see with the standard windows copy, including the gui copy. > - > Total Copied Skipped Mismatch FAILED Extras > - > ROBOCOPY :: Robust File Copy for Windows > H:\xx8>robocopy /E /NDL /NFL /NC /NS /MT:8 xx8c xx8ca That's a pretty consistent result on the ssd drive, which are more sensitive to cpu pr. Robocopy displays that it took around 14 secs, while the release build of the D commandline cpd utility took around 12 secs. > So here is the output of a batch file I just ran on the ssd drive for the 1.5GB copy. On Tuesday, 6 March 2012 at 00:29:01 UTC, Jay Norwood wrote: So, at least for these ssd drives the parallel processing results in worthwhile speed-ups. Total Copied Skipped Mismatch FAILED Extrasītw, I just ran robocopy with /mt:1, and it took around 42 seconds on the same drive, which is about what I see with the standard windows copy, including the gui copy. H:\xx8>robocopy /E /NDL /NFL /NC /NS /MT:8 xx8c xx8ca

So here is the output of a batch file I just ran on the ssd drive for the 1.5GB copy.
