On Thu, Apr 23, 2009 at 11:51 PM, SMREKAR, JACK <[email protected]> wrote:
> some one did something stupid in a programming class.
Okay, so it's not filesystem corruption. That's good.
> but is there also a way to tell what files or directories are above the limit
> or can not be deleted
From the sound of your original problem report, all you have to do
is run your backup software. ;-)
An easier method, from a command prompt:
DIR /A/S/B > NUL
"/S" to traverse subdirectories; "/A" for all files; "/B" for a bare
list. The "> NUL" discards standard output, but allows errors to be
reported. Any overly long path name will be reported as "The
directory name %s is too long". You can save the errors to a file
with:
DIR /A/S/B > NUL 2>long.txt
Then any of the methods already provided to fix the issue. I like
Tom Alverson's idea of using ROBOCOPY to mirror an empty directory.
(ROBOCOPY is not as brain damaged as the rest of Windows, and can
handle paths up to the limit of NTFS.)
-- Ben
~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
