Hi Bruce,
Since every file uses one inode, the number of files you can store is limited by the
number of inodes available. However, it is -also- limited by the amount of available
space. This means
that if you have a few very large files, you can run out of space and have inodes left
over. On the other hand, if you have lots of little files, you can run out of inodes and
still have plenty of space left over.
There's some good detail on how that works for ext4 on this wiki:
https://ext4.wiki.kernel.org/index.php/Ext4_Disk_Layout
If you're using xfs, the numbers look a little different.
Robert M. Marmorstein
Associate Professor of Computer Science
Longwood University, Ruffner 329
201 High Street, Farmville, VA 23909
434.395.2185
marmorsteinrm(a)longwood.edu
________________________________________
From: bruce <badouglas(a)gmail.com>
Sent: Friday, October 13, 2017 11:04 AM
To: Community support for Fedora users
Subject: best way to determine the "max" number of files for a drive/partition
Hey guys..
Couple of questions. (I'll split them in sep mail msgs..)
1) What's a good/easy/best approach to getting the max possible number
of files for a drive. Isn't the inode count a "good" approximation for
this.
I've got a 30G cloud instance and i'm looking to have a bunch of small
files for a process.
thanks
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org