The inode number associated to a file is changed when the file is moved inside the same file system
Answers
Answered by
0
Moving is actually creating a copy of a file in a new location, then deleting the file from its previous location. Since it is impossible to have two identical inode numbers at the same time, the inode number should change after copying and before deleting the old file (short time). However, I discovered that the inode number does not change after mv command. So, is the inode number of the deleted file reassigned to the copied file?
Answered by
0
It really does both, contingent upon the specific situation.
In case the source and target are the two records, it renames.
In case the source is a document and the objective is an index, it moves.
Be that as it may, once we comprehend the inward working of the mv charge regarding anodes, we will acknowledge both are same.
Similar questions