Question

I am doing file-upload for a web-application (running on unix/linux). I’m wondering if there would be a concern if I planned to create a new directory for each file upload? This is the out-of-the-box approach for the Ruby on Rails plugin “paperclip”. I debating what the trade-offs are, or whether perhaps it’s just not a concern, if deploying on a linux/unix environment.

The options would seem to be:

1. One folder per file attachment – per how paperclip seems to work out of the box
2. One folder per user perhaps (i.e. if web service has multiple users with their own account) – and then one would need to add some uniqueness to the filename (perhaps the model ID)
3. Put all attachments in one folder – but this is probably going too far the other way

Question – Should I be concerned about the number of directories being created? Is this an issue for an O/S if the service was popular? Any advice for a website that was allowing users with their own separate account to upload files, what structure might be good with respect to storing them? (I guess I’ve discounted the concept of storing files in mysql.)

Thanks

Answer 1

Assuming Ext3 formatted drive under Linux (the most common).

From (http://en.wikipedia.org/wiki/Ext3)

“There is a limit of 31998 sub-directories per one directory, stemming from its limit of 32000 links per inode.[13]”

So, if you’ll hit the limit of 32k uploads, which isn’t that high, your application will fail.