Tag Info

Hot answers tagged

42

Thanks to everyone for the useful advice. Straying well into StackOverflow territory, I've solved the problem by knocking up this snippet of C# code. It uses the Delimon.Win32.IO library that specifically addresses issues accessing long file paths. Just in case this can help someone else out, here's the code - it got through the ~1600 levels of recursion ...


23

Could be a recursive junction point. Such a thing can be created with junction a file and disk utility from Sysinternals. mkdir c:\Hello junction c:\Hello\Hello c:\Hello And you can now go endlessly down c:\Hello\Hello\Hello.... (well until MAX_PATH is reached, 260 characters for most commands but 32,767 characters for some Windows API functions). A ...


14

Not an answer, but I don't have enough rep for a comment. I once fixed this problem on a then-huge 500MB FAT16 disc on an MS-DOS system. I used DOS debug to manually dump and parse through the directory table. I then flipped one bit to mark the recursive directory as deleted. My copy of Dettman and Wyatt 'DOS Programmers' Reference' showed me the way. I ...


7

Java can also deal with long file paths. And it can do it a lot faster too. This code (which I copied from the Java API documentation) will delete a 1600 level deep directory structure in about 1 second (under Windows 7, Java 8.0) and with no risk of stack overflow since it doesn't actually use recursion. import java.nio.file.*; import ...


5

In the general case, you can't increase your inode limit without reformatting. ReiserFS doesn't use inodes. Don't use ReiserFS... it's as dead as Mrs. Reiser... though I suppose she'd probably prefer Mrs. Sharanova, considering.


3

If you simply want to answer the question, "what files on this system have changed", then use a tool that generates checksums for all your files. Run it before the consultant makes any changes, run it afterwards, and look for files that have changed. Store the results someone other than on the system. And of course, be aware that some files change ...


3

You don't need long pathnames if you chdir into the directory and just use relative paths to rmdir. Or, if you have a POSIX shell installed, or port this to the DOS equivalent: # untested code, didn't bother actually testing since the OP already solved the problem. while [ -d Folder1 ]; do mv Folder1/Folder1/Folder1/Folder1 tmp # repeat more times to ...


3

This sounds like a mix up of different principles. A machine named ServerName is sharing a path c:\path\to\sharename which is shared via name sharename. In this scenario, you connect to the share name remotely simply with \\ServerName\sharename - not the whole path of the share name. By default, administrators are also able to access the root of each ...


3

I am not aware of an application that will do this for you. Your most likely solution is to write a script yourself, it shouldn't really be that difficult. It appears that the source directory is in fact an NFS mount (we don't know what the destination directory is). This means that inotify can't be used. The internet suggests that FAM may be of use in ...


3

This is a classic case of trying to solve a people problem with a technical solution. Is it possible? Not as standard, no. Is there a workaround? Almost certainly, you could run a script or service to monitor the folder and rename things. Should you? In my opinion, no. Any attempt to come up with some hacky solution will only lead to excruciating pain ...


2

Look for recently modified files by using the command below. It will show the files modified during the last ten minutes inside FOLDER. Increase the -mmin -10 parameter to see how the FOLDER was modified through time. See man find and look for -mtime and -mmin for full details: sudo find FOLDER -xdev -type f -mmin -10 -ls Another situation is when deleted ...


2

You can use vmtouch for this... To see how much of SYSERR.TXT is in the file system cache, [root@GreenLeaf /ppro/data]# vmtouch -v SYSERR.TXT SYSERR.TXT [OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO] 1859/1859 Files: 1 Directories: 0 Resident Pages: 1859/1859 7M/7M 100% Elapsed: 0.000316 seconds 100% of it ...


1

You can try iotop tool which shows you I/O usage by processes (in other words, which top processes are using your disk), so you can track which process is responsible for eating the space. Another way is to use inotify (part of inotify-tools) which can monitor directories for changes. Or simple way is to use du in the following way. Define the following ...



Only top voted, non community-wiki answers of a minimum length are eligible