And that is almost certainly what I'm looking for.

I'll try that tomorrow.

Thank you sir.

Kurt

On Mon, Aug 2, 2010 at 18:21, Andrew S. Baker <[email protected]> wrote:
> Powershell...
>  dir C:\Temp -force | format-table -property CreationTime, Length, Name
>  dir C:\Temp -force | format-table -property LastWriteTime, Length, Name
>  dir C:\Temp -force | format-table -property LastAccessTime, Length, Name
>
> ASB (My XeeSM Profile)
> Exploiting Technology for Business Advantage...
>
>
> Signature powered by WiseStamp
>
> On Mon, Aug 2, 2010 at 9:07 PM, Andrew S. Baker <[email protected]> wrote:
>>
>> for %V in (C:\Temp\*.*) do @echo %~tV %~zV %~V
>> This is only the regular modified date of the file, though.
>>
>> PowerShell can do what you want, but I'd have to play with that longer to
>> tell you...
>>
>> ASB (My XeeSM Profile)
>> Exploiting Technology for Business Advantage...
>>
>>
>> Signature powered by WiseStamp
>>
>> On Mon, Aug 2, 2010 at 8:48 PM, Kurt Buff <[email protected]> wrote:
>>>
>>> All,
>>>
>>> On our file server we have a single 1.5tb partition - it's on a SAN.
>>> Over the course of 4 days recently it went from about 30% free to
>>> about 13% free - someone slammed around 200gb onto the file server.
>>>
>>> I have a general idea of where it might be - there are two top-level
>>> directories that are over 200gb each.
>>>
>>> However, windirstat hasn't been completely helpful, as I can't seem to
>>> isolate which files were loaded during those days, and none of the
>>> files that I've been looking at were huge - no ISO or VHD files worth
>>> mentioning, etc..
>>>
>>> I also am pretty confident that there are a *bunch* of duplicate files
>>> on those directories.
>>>
>>> So, I'm looking for a couple of things:
>>>
>>> 1) A way to get a directory listing that supports a time/date stamp
>>> (my choice of atime, mtime or ctime) size and a complete path name for
>>> each file/directory on a single line - something like:
>>>
>>>     2009-01-08  16:12   854,509
>>> K:\Groups\training\On-Site_Special_Training\Customer1.doc
>>>
>>> I've tried every trick I can think of for the 'dir' command and it
>>> won't do what I want, and the 'ls' command from gunuwin32 doesn't seem
>>> to want to do this either. Is there a powershell one-liner that can do
>>> this for me perhaps?
>>>
>>> 2) A recommendation for a duplicate file finder - cheap or free would
>>> be preferred.
>>>
>>> Kurt
>>>
>>> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
>>> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
>>
>
>
>
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to