New answers tagged inode
Given EXT4 is journaled, it's unlikely that you lost any data in the process. Having orphaned inodes after an abnormal shutdown is normal (see Serverfault) so those inodes are probably related to temporary files that won't give you much back if you were able to recover them. In short, you probably could, but it's unlikely you'd want them.
To list the detailed inode usage for '/' use the following command : echo "Detailed Inode usage for: $(pwd)" ; for d in find -maxdepth 1 -type d |cut -d\/ -f2 |grep -xv . |sort; do c=$(find $d |wc -l) ; printf "$c\t\t- $d\n" ; done ; printf "Total: \t\t$(find $(pwd) | wc -l)\n"
The PHP documentation sucks is very bad: vague, ambiguous, and misleading. fileinode() is tersely defined as “gets file inode” or “returns the inode”. But if you dig a little deeper, the documentation seems to start saying that this function returns the inode number. An inode is more than an inode number. The difference between “returning the inode of a ...
You can't use inode to check if a file has been changed. It may or may not change when a file is renamed, or moved. It will typically stay the same unless moved onto another disk ...
An inode used to be the on-disk structure that contained access permissions, ownership, size in bytes, and the disk block numbers of the disk blocks that contained a file's data. So, some metadata, and some data. The file's name was just an entry in a specially-marked file, called a "directory". The name was associated with the "inode number". ...
A file rename that doesn't cross file system boundaries is just a metadata change, so it should preserve the inode number. Generally speaking, opening a file and modifying its contents should not change its inode number, which only makes sense within a single file system anyway (but it will change the access times, for example). Note that some tools such as ...
Top 50 recent answers are included