Timeline for How does Linux know the Location of File Data on Disk
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 1, 2013 at 22:09 | comment | added | naftalimich | Wow perfect. Most complete answer by far. | |
| May 1, 2013 at 20:59 | comment | added | derobert | @naftalimich The superblock gives the parameters which determine the layout of the filesystem (these are set at mkfs time). You can you dumpe2fs to see them. Using those parameters, you can translate an inode number to a position on disk (that stores the actual inode). You can then read the inode (from disk)—that's where that metadata is. An i-number or inode number is an integer that specifies which i-node. A i-node is a data structure. | |
| May 1, 2013 at 18:22 | comment | added | naftalimich | Will look into the docs but am trying to navigate the beginning and end of your first paragraph: ..."The inode contains a lot of metadata [...]" Is this after translating it with the superblock info or is this an alternative implementation? | |
| May 1, 2013 at 17:20 | history | answered | derobert | CC BY-SA 3.0 |