Lines Matching +full:block +full:- +full:size

38 .I "super-block" .
39 The super-block is built when the file system is created (\c
42 The super-block
46 Because the super-block contains critical data,
50 .I "default super block"
56 or other hard disk error causes the default super-block
74 the range 5-13.
77 containing further data block indices.
78 In a file system with a 4096 byte block size, a singly indirect
79 block contains 1024 further block addresses,
80 a doubly indirect block contains 1024 addresses of further single indirect
82 and a triply indirect block contains 1024 addresses of further doubly indirect
83 blocks (the triple indirect block is never needed in practice).
88 the minimum size of a file system block is 4096 bytes.
89 The size of file system blocks can be any power of two
91 The block size of the file system is maintained in the super-block,
92 so it is possible for file systems of different block sizes
94 The block size must be decided when
97 the block size cannot be subsequently
102 Associated with the super block is non replicated
116 .I "block map"
131 could cause the loss of all copies of the redundant super-blocks.
146 or platter can be lost without losing all copies of the super-blocks.
155 file system block into one or more
159 each file system block can be optionally broken into
161 The lower bound on the size of these fragments is constrained
162 by the disk sector size;
163 typically 512 bytes is the lower bound on fragment size.
164 The block map associated with each cylinder group
167 to determine block availability.
169 On a file system with a block size of 4096 bytes
170 and a fragment size of 1024 bytes,
172 and possibly a single fragmented block.
173 If a file system block must be fragmented to obtain
175 the remainder of the block is made available for allocation
180 This file uses two full size blocks and a 3072 byte fragment.
183 a full size block is split yielding the necessary 3072 byte
210 .I "in-core"
223 lags the state of the file system represented by the in-core information.
225 The disk information is updated to reflect the in-core information
234 If the system is halted without writing out the in-core information,
239 One inconsistency is that a block may be claimed by two inodes.
241 the pointer to the block in the old inode has been cleared
243 and after the pointer to the block in the new inode has been written out
247 which inode should really claim the block.