Lines Matching +full:block +full:- +full:number

42 physically write-protecting a mounted file system,
43 or a mounted file system is taken off-line.
57 can be as subtle as a bad block
58 on a disk pack, or as blatant as a non-functional disk-controller.
64 is run non-interactively.
96 is a multi-pass program.
104 Super-block checking
108 associated with the super-block.
115 The super-block is checked for inconsistencies
116 involving file-system size, number of inodes,
117 free-block count, and the free-inode count.
118 The file-system size must be larger than the
119 number of blocks used by the super-block
120 and the number of blocks used by the list of inodes.
121 The file-system size and layout information
132 detects corruption in the static parameters of the default super-block,
134 requests the operator to specify the location of an alternate super-block.
136 Free block checking
140 marked as free in the cylinder group block maps
145 the number of free blocks
146 plus the number of blocks claimed by the inodes
147 equals the total number of blocks in the file system.
149 If anything is wrong with the block allocation maps,
154 The summary information associated with the super-block
155 counts the total number of free blocks within the file system.
158 number of free blocks it found within the file system.
162 by the actual free-block count.
165 counts the total number of free inodes within the file system.
167 compares this count to the number
172 summary information by the actual free-inode count.
178 However, because of the great number of active inodes,
197 special block inode, special character inode, or socket inode.
210 total number of directory entries
219 If the stored link count is non-zero and the actual
227 If the stored and actual link counts are non-zero and unequal,
243 compares each block number claimed by an inode
245 If another inode already claims a block number,
246 then the block number is added to a list of
249 is updated to include the block number.
255 to find the inode of the duplicated block.
273 checks the range of each block number claimed by an inode.
274 If the block number is
275 lower than the first data block in the file system,
276 or greater than the last data block,
277 then the block number is a
278 .I "bad block number" .
280 an indirect block that was not written to the file system,
282 If an inode contains bad block numbers,
288 Each inode contains a count of the number of data blocks
290 The number of actual data blocks
294 computes the actual number of data blocks
295 and compares that block count against
296 the actual number of blocks the inode claims.
301 Each inode contains a thirty-two bit size field.
302 The size is the number of data bytes
305 by computing from the size field the maximum number of blocks
307 and comparing that expected block count against
308 the actual number of blocks the inode claims.
325 Each directory data block is checked for
330 the number of inodes in the file system,
333 If the inode number in a directory data block
348 last allocated block preceding the hole.
352 directory containing an unallocated block.
354 If a directory entry inode number references
358 This condition occurs if bad data is written into a directory data block.
360 The directory inode number entry for ``\fB.\fP''
361 must be the first entry in the directory data block.
362 The inode number for ``\fB.\fP''
364 e.g., it must equal the inode number
365 for the directory data block.
366 The directory inode number entry
368 the second entry in the directory data block.
369 Its value must equal the inode number for the
371 (or the inode number of the directory
372 data block if the directory is the
402 the National Science Foundation under grant MCS80-05144,
405 Contract No. N00039-82-C-0235. (Kirk McKusick, July 1983)
432 pp. 181-197, August 1984.
435 The UNIX Time-Sharing System,
438 6 (July-August 1978, Part 2), pp. 1905-29.
444 6 (July-August 1978, Part 2), pp. 1931-46.