Home | History | Annotate | Download | only in doc

Lines Matching full:blocks

192 <Title>About blocks and block groups</Title>
196 into small units called <Literal remap="tt">blocks</Literal>. A block is the smallest unit which
214 Ext2fs groups together a fixed number of sequential blocks into a <Literal remap="tt">group
216 series of group blocks. This is done in order to keep related information
218 much of the filesystem management reduces to management of a single blocks
225 <Title>The view of inodes from the point of view of a blocks group</Title>
230 much like a <Literal remap="tt">block</Literal> - Each blocks group contains a limited number of
241 Each blocks group is accompanied by a <Literal remap="tt">group descriptor</Literal>. The group
252 __u32 bg_block_bitmap; /* Blocks bitmap block */
255 __u16 bg_free_blocks_count; /* Free blocks count */
266 The last three variables: <Literal remap="tt">bg&lowbar;free&lowbar;blocks&lowbar;count, bg&lowbar;free&lowbar;inodes&lowbar;count and bg&lowbar;used&lowbar;dirs&lowbar;count</Literal> provide statistics about the use of the three
267 resources in a blocks group - The <Literal remap="tt">blocks</Literal>, the <Literal remap="tt">inodes</Literal> and the
269 the load between the various blocks groups.
275 specific blocks group.
286 <Literal remap="tt">inode table of the current blocks group</Literal>. The <Literal remap="tt">inode table</Literal> is
301 Each blocks group contains the entire table of group descriptors in its
313 Each blocks group contains one special block which is actually a map of the
314 entire blocks in the group, with respect to their allocation status. Each
326 1024*8=8192 blocks in a group block. This number is one of the fields in the
336 Block 0 in the blocks group is managed by bit 0 of byte 0 in the bitmap
343 Block 7 in the blocks group is managed by bit 7 of byte 0 in the bitmap
350 Block 8 in the blocks group is managed by bit 0 of byte 1 in the bitmap
357 Block 8191 in the blocks group is managed by bit 7 of byte 1023 in the
376 blocks, since the physical device is usually optimized to handle such a close
389 inodes then blocks in a blocks group and thus only part of the inode bitmap
390 block is used. The number of inodes in a blocks group is another variable
430 be free blocks on the filesystem.
440 number of inodes and is placed at a different blocks group. The goal is to
441 place inodes and their related files in the same blocks group because of
446 The number of inodes in a blocks group is available in the superblock variable
454 blocks group which contains the table.
474 __u32 i_blocks; /* Blocks count */
487 __u32 i_block[EXT2_N_BLOCKS];/* Pointers to blocks */
520 <Title>The allocated blocks</Title>
524 allocated blocks. There is no limitation on the allocated blocks - Each
531 of blocks, assuming that the current inode type indeed refers to a list of
532 allocated blocks.
538 storage of up to 12 block numbers in the inode itself. Those blocks are
539 called <Literal remap="tt">direct blocks</Literal>. The advantage is that once the kernel has the
540 inode, it can directly access the file's blocks, without an additional disk
541 access. Those 12 blocks are directly specified in the variables
548 list of direct blocks. For example, if the block size is 1024 bytes, since
550 blocks. That is, block 13 till block 268 in the file will be accessed by the
552 direct blocks case, is that an additional access to the device is needed -
563 blocks. Each one of them is handled in the way described above.
568 of indirection - It will point to a list of double indirect blocks.
804 When this bit is on, the file's blocks are zeroed when the file is
942 accessing additional blocks. It is also economical, since it allocates only
998 Inode 1 is the <Literal remap="tt">bad blocks inode</Literal> - I believe that its data
999 blocks contain a list of the bad blocks in the filesystem, which
1059 the direct blocks, indirect blocks, etc) - It is just a file which is
1121 The superblock, like the group descriptors, is copied on each blocks group
1165 __u32 s_blocks_count; /* Blocks count */
1166 __u32 s_r_blocks_count; /* Reserved blocks count */
1167 __u32 s_free_blocks_count; /* Free blocks count */
1172 __u32 s_blocks_per_group; /* # Blocks per group */
1187 __u16 s_def_resuid; /* Default uid for reserved blocks */
1188 __u16 s_def_resgid; /* Default gid for reserved blocks */
1229 <Literal remap="tt">s&lowbar;blocks&lowbar;count</Literal> contains the total number of available blocks.
1243 <Literal remap="tt">s&lowbar;blocks&lowbar;per&lowbar;group</Literal> contains the number of blocks which are grouped
1244 together as a blocks group.
1250 number of blocks groups.
1291 <Literal remap="tt">s&lowbar;log&lowbar;block&lowbar;size</Literal> and <Literal remap="tt">s&lowbar;blocks&lowbar;per&lowbar;group</Literal>, respectively.
1415 <Literal remap="tt">s&lowbar;r&lowbar;blocks&lowbar;count</Literal> contains the number of disk blocks which are
1418 allocate those last <Literal remap="tt">s&lowbar;r&lowbar;blocks&lowbar;count</Literal> if the user is not one of the
1425 of the group who can use the reserved blocks in addition to root.
1434 <Literal remap="tt">s&lowbar;free&lowbar;blocks&lowbar;count</Literal> contains the current number of free blocks