Lines Matching full:are
11 filesystem in use by Linux. There are also implementations available
17 Most defaults are determined by the filesystem superblock, and can be
18 set using tune2fs(8). Kernel-determined defaults are indicated by (*).
80 compression though these are not yet implemented (some are available as
88 The space in the device or file is split up into blocks. These are
97 Blocks are clustered into block groups in order to reduce fragmentation
101 Two blocks near the start of each group are reserved for the block usage
103 are in use. Since each bitmap is limited to a single block, this means
106 The block(s) following the bitmaps in each block group are designated
107 as the inode table for that block group and the remainder are the data
118 the superblock are stored in block groups throughout the filesystem.
124 superblock feature). The groups chosen are 0, 1 and powers of 3, 5 and 7.
127 number of inodes and blocks in the filesystem and how many are free,
128 how many inodes and blocks are in each block group, when the filesystem
133 If the filesystem is revision 1 or higher, then there are extra fields,
137 All fields in the superblock (as in all other ext2 structures) are stored
153 There are some reserved fields which are currently unused in the inode
154 structure and several which are overloaded. One field is reserved for the
164 There are pointers to the first 12 blocks which contain the file's data
173 behaviour on a per-file basis. There are flags for secure deletion,
176 of these are supported yet.
189 The inode allocation code tries to assign inodes which are in the same
190 block group as the directory in which they are first created.
202 Symbolic links are also filesystem objects with inodes. They deserve
207 block for the symlink, and most symlinks are less than 60 characters long.
242 revision 1. There are three 32-bit fields, one for compatible features
296 scheme but less reliable. Both methods are equally resolvable by their
299 If you're exceptionally paranoid, there are 3 ways of making metadata
306 the first and last are not ext2 specific but do force the metadata to
312 There are various limits imposed by the on-disk layout of ext2. Other
313 limits are imposed by the current implementation of the kernel code.
314 Many of the limits are determined at the time the filesystem is first
334 so 8kB blocks are only allowed on Alpha systems (and other architectures
348 is over 130 trillion files. It would be higher except there are not
350 have to be 8 character filenames, even then we are fairly close to
365 When changes to the filesystem (e.g. a file is renamed) they are stored in
369 in that transaction are guaranteed to represent a valid filesystem state,
370 and are copied into the filesystem. If a transaction is incomplete at
372 the blocks in that transaction so they are discarded (which means any
373 filesystem changes they represent are also lost).