New answers tagged inode
I really can't stress this enough, don't create a boatload of inodes! First your fsck runtime can be lengthened exponentially, although some of those concerns were addressed in ext4. More importantly, inodes aren't the only limiting file number factor, it's likely impossible to use all those inodes. This isn't just practically speaking, it may actually be ...
Here's a compilation of some useful listing commands (re-hashed based on previous users code): List folders with file count: find -maxdepth 1 -type d | sort | while read -r dir; do n=$(find "$dir" -type f | wc -l); printf "%4d : %s\n" $n "$dir"; done List folders with non-zero file count: find -maxdepth 1 -type d | sort | while read -r dir; do n=$(find ...
No. Directory entries pointing to inodes are one-way links. The inodes do not point back to the directory entries. In order to find a complete list of directory entries that point to an inode, you need to traverse the filesystem until you have found enough directory entries to account for the inode's link count.
That is a really bad idea. Every inode consumes 256 bytes (may be configured as 128). Thus just the inodes would consume 1TiB of space. Other file systems like btrfs can create inodes dynamically. Use one of them instead.
See here: How does Linux know the Location of File Data on Disk The addition being that inodes also, in one way or another, store the actual location of the file's data bits on disk.
If you already have the inode number you can use find's -inum option: find -inum 12353538
find -samefile /mount/point/your/file
Top 50 recent answers are included