this post was submitted on 23 Jul 2024
32 points (86.4% liked)
Programming
24607 readers
207 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Why waste the inodes?
This is also going to make some devs (me) convulse when a PR is like, "small config change. updated 29 files".
I have one that has 69 (noice) files changed.
That was my first reaction just by reading the title.
Mostly because I learned the hard way what inodes are.
Read the content. I address that issue.
For the record, you mention "the limitations of the number of inodes in Unix-like systems", but this is not a limit in Unix, but a limit in filesystem formats (which also extends to Windows and other systems).
So it depends more on what the filesystem is rather than the OS. A FAT32 partition can only hold 65,535 files (2^16), but both ext4 and NTFS can have up to 4,294,967,295 (2^32). If using Btrfs then it jumps to 18,446,744,073,709,551,615 (2^64).
You are right. Fat32 is not recommended for implementing FAMF.
I know, I read it because I wanted to know too know if it was addressed
What would you do with billions of inodes?
Run out, far more frequently than you would imagine.
Well I'd you have so many data entry, yaml and toml are not that helpful either. They would present different sets of problems. You should use a database (perhaps sqlite) for that purpose.