Lines Matching full:group
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
219 group.
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
238 <Title>The group descriptors</Title>
241 Each blocks group is accompanied by a <Literal remap="tt">group descriptor</Literal>. The group
242 descriptor summarizes some necessary information about the specific group
243 block. Follows the definition of the group descriptor, as defined in
267 resources in a blocks group - The <Literal remap="tt">blocks</Literal>, the <Literal remap="tt">inodes</Literal> and the
275 specific blocks group.
286 <Literal remap="tt">inode table of the current blocks group</Literal>. The <Literal remap="tt">inode table</Literal> is
296 The group descriptors are placed one after the other. Together they make the
297 <Literal remap="tt">group descriptors table</Literal>.
301 Each blocks group contains the entire table of group descriptors in its
303 group 0) is actually used by the kernel. The other copies are there for
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
316 group is used or free.
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
375 the kernel on purpose in order to group related data in physically 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
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
447 <Literal remap="tt">s_inodes_per_group</Literal>. For example, if there are 2000 inodes per group,
448 group 0 will contain the inodes 1-2000, group 2 will contain the inodes
453 Each inode table is accessed from the group descriptor of the specific
454 blocks group which contains the table.
472 __u16 i_gid; /* Group Id */
523 The basic functionality of an inode is to group together a series of
595 the group and digit 2 to everyone else. They are used by the kernel to grant
616 Bit number 10 signals that the file is <Literal remap="tt">set group id</Literal> - I don't know
747 <Title>User and group id</Title>
750 The user and group id of the file are just saved in the variables
1121 The superblock, like the group descriptors, is copied on each blocks group
1172 __u32 s_blocks_per_group; /* # Blocks per group */
1173 __u32 s_frags_per_group; /* # Fragments per group */
1174 __u32 s_inodes_per_group; /* # Inodes per group */
1203 versions; Specifically, the group descriptors definition is different. I
1243 <Literal remap="tt">s_blocks_per_group</Literal> contains the number of blocks which are grouped
1244 together as a blocks group.
1248 <Literal remap="tt">s_inodes_per_group</Literal> contains the number of inodes available in a group
1290 <Literal remap="tt">s_log_frag_size</Literal> and <Literal remap="tt">s_frags_per_group</Literal> are always equal to
1291 <Literal remap="tt">s_log_block_size</Literal> and <Literal remap="tt">s_blocks_per_group</Literal>, respectively.
1417 group whose id number is <Literal remap="tt">s_deg_resgid</Literal>. The kernel will refuse to
1425 of the group who can use the reserved blocks in addition to root.
