Lines Matching full:inode
228 Each file in the filesystem is reserved a special <Literal remap="tt">inode</Literal>. I don't want
231 inode, while any specific inode can be <Literal remap="tt">allocated</Literal> or
279 <Literal remap="tt">bg_inode_bitmap</Literal> is fully analogous to the previous variable - It
280 contains the block number of the <Literal remap="tt">inode allocation bitmap block</Literal>, which
281 is used to allocate / deallocate each specific inode in the filesystem.
285 <Literal remap="tt">bg_inode_table</Literal> contains the block number of the start of the
286 <Literal remap="tt">inode table of the current blocks group</Literal>. The <Literal remap="tt">inode table</Literal> is
291 The block bitmap block, inode bitmap block and the inode table are created
383 <Title>The inode allocation bitmap</Title>
386 The format of the inode allocation bitmap block is exactly like the format of
388 the work <Literal remap="tt">block</Literal> replaced by <Literal remap="tt">inode</Literal>. Typically, there are much less
389 inodes then blocks in a blocks group and thus only part of the inode bitmap
397 <Title>On the inode and the inode tables</Title>
400 An inode is a main resource in the ext2 filesystem. It is used for various
422 Each file, for example, will allocate one inode from the filesystem
434 Each inode takes up 128 bytes in the filesystem. By default, <Literal remap="tt">mke2fs</Literal>
435 reserves an inode for each 4096 bytes of the filesystem space.
453 Each inode table is accessed from the group descriptor of the specific
458 Follows the structure of an inode in Ext2fs:
523 The basic functionality of an inode is to group together a series of
525 block can be allocated to each inode. Nevertheless, block allocation will
530 The inode is not always used in that way. I will now explain the allocation
531 of blocks, assuming that the current inode type indeed refers to a list of
538 storage of up to 12 block numbers in the inode itself. Those blocks are
540 inode, it can directly access the file's blocks, without an additional disk
577 The i_mode variable is used to determine the <Literal remap="tt">inode type</Literal> and the
596 or deny access to the object presented by this inode.
611 the inode as file even though it can be a special device, for example) is
637 options. They determine the type of the "file" to which the inode belongs:
704 <Literal remap="tt">i_ctime</Literal> - The time in which the inode was last allocated. In
723 <Literal remap="tt">i_dtime</Literal> - The time in which the inode was deallocated. In
739 the inode. If the inode corresponds to a regular file, this is just the size
761 explained that each <Literal remap="tt">directory entry</Literal> points to an inode. It is quite
762 possible that a <Literal remap="tt">single inode</Literal> will be pointed to from <Literal remap="tt">several</Literal>
770 inode, and is incremented with each additional link. Deletion of a file will
772 Only when this number reaches zero, the inode will be actually deallocated.
787 The ext2 filesystem associates additional flags with an inode. The extended
806 original data when the inode is deallocated.
875 inode. The important aspect is that the inode number is <Literal remap="tt">fixed</Literal> when
889 since a hard link is just an inode number in some directory entry,
899 "replacement" will not deallocate the original inode, but rather
900 allocate another inode for the new version, and the directory entry
901 at the other place will just point to the old inode number.
911 symbolic link is just a <Literal remap="tt">pathname</Literal> which is accessible from an inode.
926 inode, and can also consume one block.
930 When the inode is identified as a symbolic link, the kernel needs to find
939 inode, on the <Literal remap="tt">i_block[0] - i_block[15]</Literal> variables, since those are not
941 because the pathname resolution can be done using the inode itself, without
943 an inode. The length of the pathname is stored in the <Literal remap="tt">i_size</Literal>
998 Inode 1 is the <Literal remap="tt">bad blocks inode</Literal> - I believe that its data
1006 Inode 2 is the <Literal remap="tt">root inode</Literal> - The inode of the root directory.
1013 Inode 3 is the <Literal remap="tt">acl index inode</Literal>. Access control lists are
1015 inode is not used.
1021 Inode 4 is the <Literal remap="tt">acl data inode</Literal>. Of course, the above applies
1028 Inode 5 is the <Literal remap="tt">boot loader inode</Literal>. I don't know its
1035 Inode 6 is the <Literal remap="tt">undelete directory inode</Literal>. It is also a
1071 __u32 inode; /* Inode number */
1097 The <Literal remap="tt">inode</Literal> variable points to the inode of the above file.
