Most helpful thought that comes to mind at this point is to use robocopy with the /l switch. It'll be faster, and you won't run into limitations with the path length.
If you need to parse the output, powershell would be useful for that. STFW for powershell and robocopy - there are some reasonable examples. Kurt On Fri, Mar 18, 2016 at 12:35 PM, Orlebeck, Geoffrey <[email protected]> wrote: > We have a unique situation where one of our NAS appliances is showing > ~3GB/hr growth for the last ~7days. We recently lost our SAN/NAS > administrator, so the rest of us are a bit unsure how to proceed. My initial > thought as a cursory check was to try (quickly) to get an idea of the root > shares sizes and check which ones are growing the fastest, then try to > narrow focus onto them. I understand this may require going to the .NET > level and not using simple Get-ChildItem, etc. due to the Path character > limit. > > > > I’m just trying to figure out the best way to (as quickly as possible) > obtain a basic folder size at the root of some shares and then re-run that > check every one or two or three hours to determine where the growth is. We > have a support case open with the NAS vendor, but in the meantime the > current growth would mean we run out of space in ~10 days. Just looking for > some ideas on how to accomplish this. > > > > We have an account with access to the root share that all others come from, > so we can crawl all of them or individual ones in separate jobs/threads. But > again, it’s a little beyond my current knowledge level with PowerShell. > > > > Any helpful thoughts/tips are appreciated. > > Confidentiality Notice: This is a transmission from Community Hospital of > the Monterey Peninsula. This message and any attached documents may be > confidential and contain information protected by state and federal medical > privacy statutes. They are intended only for the use of the addressee. If > you are not the intended recipient, any disclosure, copying, or distribution > of this information is strictly prohibited. If you received this > transmission in error, please accept our apologies and notify the sender. > Thank you. > > ================================================ > Did you know you can also post and find answers on PowerShell in the forums? > http://www.myitforum.com/forums/default.asp?catApp=1 ================================================ Did you know you can also post and find answers on PowerShell in the forums? http://www.myitforum.com/forums/default.asp?catApp=1
