Accidentally quadratic: rm -rf??

June 24th, 2015

This is a REALLY bad time. Please please PLEASE tell me I'm not fucked...

I've accidentally created about a million files in a directory.¬†Now ls takes forever, Python's os.listdir¬†is faster but still dog-slow ‚Äď but! but! there's hope ‚Äď a C loop program using opendir/readdir is reasonably fast.

Now I want to modify said program so that it removes those files which have a certain substring in their name. (I want the files in that directory and its subdirectories, just not the junk I created due to a typo in my code.)

HOW THE FUCK DO I DO THAT IN O(N)??

O(N^2) is easy enough.¬†The unlink function takes a filename, which means that under the hood it reads ALL THE BLOODY FILE NAMES IN THAT DIRECTORY until it finds the right one and THEN it deletes that file. Repeated a million times, that's a trillion operations ‚Äď a bit less because shit gets divided by 2 in there, but you get the idea.

Now, readdir gives me the fucking inode number. How the FUCK do I pass it back to this piece of shit operating system from hell, WITHOUT having it search through the whole damned directory AGAIN to find  what it just gave me?

I would have thought that rm -rf for instance would be able to deal with this kind of job efficiently. I'm not sure it can. The excise function in the guts of coreutils for instance seems to be using unlinkat which gets a pathname. All attempts to google for this shit came up with advice to use find -inode -exec rm or some shit like that, which means find converts inode to name, rm gets the name, Unix converts the name back to inode...

So am I correct in that:

Please tell me I'm wrong about the first 2 points, especially the second... Please please please... I kinda need those files in there...

(And I mean NOTHING, nothing at all works in such a directory at a reasonable speed because every time you need to touch a file the entire directory is traversed underneath... FUUUUUCK... I guess I could traverse it in linear time and copy aside somehow though... maybe that's what I'd do...)

Anyway, a great entry for the Accidentally Quadratic blog I guess...

Update: gitk fires up really damn quickly in that repository, showing all the changes. Hooray! Not the new files though. git citool is kinda... sluggish. I hope there were no new files there...

Updates: