Talk:Inode pointer structure

Computing: Software Start‑class Low‑importance

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing
Start	This article has been rated as Start-class on Wikipedia's content assessment scale.
Low	This article has been rated as Low-importance on the project's importance scale.
	This article is supported by WikiProject Software (assessed as Low-importance).

Linux Start‑class Low‑importance

	Linux portal This article is within the scope of WikiProject Linux, a collaborative effort to improve the coverage of Linux on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.LinuxWikipedia:WikiProject LinuxTemplate:WikiProject LinuxLinux
Start	This article has been rated as Start-class on Wikipedia's content assessment scale.
Low	This article has been rated as Low-importance on the project's importance scale.

There seems to be a contradiction in the page. First, a bullet says: "Twelve pointers that directly point to blocks of the file's data (direct pointers)" But later: "For example, a 10 block file (probably less than 80 kB in size) would be described using just the inode because its 10 blocks fit in to the ten direct pointers. However an 11 block file needs the inode in addition to an indirect block to contain the eleventh address." Doesn't this imply that there are only 10 direct blocks? I'm afraid I'm not knowledgeable enough to resolve this myself.

Yes--corrected.(Schultkl (talk) 01:47, 27 January 2010 (UTC))[reply]

Review for Stub

Even if this have "just a few lines of text". For this topic I do not think the the article contains enough facts to provide an encyclopedic coverage. Please review and mark as {{compu-storage-stub}} if it's necessary. Hashan 11:50, 19 July 2012 (UTC)

Correction and clarification requested

In the "Ease of data location" section you have "For example, if each block is 8 kB, file data at 120 to 128 kB would be pointed to by the fourth pointer of the first indirect block (assuming twelve direct pointers in the inode pointer structure)."

Correction: Shouldn't this be "120 to 127 kB" because 120 is counted as the first kB?

Also can you please clarify why its the fourth pointer instead of the third pointer? Because 120/8=15 pointers so 1 to 12 will be direct pointers and the 13th pointer would point to the first indirect block which would have the 13th, 14th and 15th pointers. But the reason why I think you said it's the fourth is because I'm assuming that the pointers start at 0 at the 0kB memory address (making a total of 16 pointers) so in that case the fourth pointer would be correct. If this is so, can this be stated explicitly in on the page? Jmarbas (talk) 06:57, 13 June 2016 (UTC)[reply]

"Many" and "most" qualifiers, without examples

The article currently claims that the 15-pointer structure is used by "many related file systems", and also claims that "most modern file systems use fifteen pointers." But the article offers only ext3 as the solitary example of a file system using 15 pointers. Are there other such systems? If so, which? And for contrast, what are some examples of file systems that *don't* use the specific layout described in this article? (I would hope the "most modern file systems" bucket includes things like ZFS and btrfs but excludes things like FAT32? Or... what?) --Quuxplusone (talk) 23:16, 9 September 2017 (UTC)[reply]