Lines Matching full:blocks

50 The size of file system blocks can be any power of two
68 a bit map describing available blocks in the cylinder group,
69 and summary information describing the usage of data blocks
71 The bit map of available blocks in the cylinder group replaces
96 is used for data blocks.\(dg
101 with blocks sizes of 16 kilobytes or greater.
109 Without knowing the size of the file system blocks,
116 Data is laid out so that larger blocks can be transferred
119 composed of 4096 byte data blocks.
120 In the old file system this file would be composed of 1024 byte blocks.
125 4096 byte blocks may be allocated from the same cylinder so that
129 larger blocks is that most UNIX
161 45.6% waste with 4096 byte file system blocks.
163 To be able to use large blocks without undue waste,
189 Figure 1 \- Example layout of blocks and fragments in a 4096/1024 file system.
198 Fragments of adjoining blocks cannot be used as a full block,
206 a file is represented by zero or more 4096 byte blocks of data,
214 This file would uses two full size blocks and one
237 The file contains no fragmented blocks (and the last
295 A file system with 4096 byte blocks and 512 byte fragments
304 more space for keeping track of available free blocks.
314 blocks that should be free.
315 If the number of free blocks drops below this level
316 only the system administrator can continue to allocate blocks.
321 If the number of free blocks falls to zero,
324 blocks in a file.
353 so that blocks can be allocated in an
366 the new file system tries to allocate new blocks
368 Optimally, these new blocks will also be
370 The distance between ``rotationally optimal'' blocks varies greatly;
376 two consecutive disk blocks can often be accessed
386 the number of blocks per track and the rate at which
394 the allocation routines calculate the number of blocks to
403 To ease the calculation of finding rotationally optimal blocks,
405 a count of the available blocks in a cylinder
430 If a file system is parameterized to lay out blocks with
449 the placement of new inodes and data blocks.
454 because there are insufficient blocks left
458 lay out data blocks.
507 The other major resource is data blocks.
508 Since data blocks for a file are typically accessed together,
510 blocks for a file in the same cylinder group,
512 The problem with allocating all the data blocks
532 file has used about 25% of the data blocks in a cylinder group.
538 groups that have a greater than average number of free blocks left.
545 requests for specific blocks.
552 they could always request unused blocks and
569 If there are no blocks available on the same cylinder,
584 space typically have so few free blocks that almost any