Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm working on a new project, for which I will need to access a large (anywhere up to 1000's) quantity of very small files (probably a median size of under 100B). I need to maintain access permissions (read and write for owner, group, and other), although executable permissions are not necessary. I must be able to arrange these files in a hierarchy structure. It is likely that files sharing a directory will most often be used together.
So, I realize that I have two main options - an archive or a file system. If I choose a file-system, it will be loop-mounted. I considered a file system with a very small block size. If I chose a file system, I think I would either use ext2 for its simplicity or reiserFS for its claims of good performance with small files. If I choose an archive, I like the compression of zip, but the portability of tar.
Suggestions? Could a database be a better solution? The primary goal is good access times and reducing the number of disk reads.
P.S. Is it possible to use a file lock on a file inside an archive? It would be a nice feature, but it can be done without.
Okay, I've changed my needs bit for this project and, I think, effectively answered my own question. Instead of a large quantity of small files, I'll really just need a smaller quantity of more average sized files. However, the ability to lock a file has gone from "would be nice" to a requirement. I think that rules out an archive, so I'm back to a file system. I'll probably be using ext2, unless reiserFS really blows me away.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.