Lines Matching refs:that

11 is this very scalability that causes the verification problem.
23 manual task of verifying that things like single bit errors or misplaced writes
29 to analyse and so that analysis blows out towards weeks/months of forensic work.
31 up, the more likely that the cause will be lost in the noise.  Hence the primary
39 One of the problems with the current metadata format is that apart from the
46 verification of metadata values, looking for values that are in range (and hence
56 ensure that common types of errors are easily detectable.  Hence the concept of
59 The first, fundamental requirement of self describing metadata is that the
76 integrity checking. We cannot trust the metadata if we cannot verify that it has
85 fast. So while CRC32c is not the strongest of possible integrity checks that
92 Self describing metadata needs to contain enough information so that the
101 block belongs to. We already know the type, the location, that it is valid
102 and/or corrupted, and how long ago that it was last modified. Knowing the owner
106 filesystem to find the owner of the block. Worse, the corruption could mean that
124 events that lead to the eventual failure, and even whether there are corruptions
125 present that the run-time verification is not detecting.
129 when the free space btree block that contains the block was last written
132 very good chance that the block should have been removed from the owner.
137 thing that resets it is running xfs_repair on the filesystem. Further, by use of
153 modification process, and seeks only to check that the metadata is what it says
154 it is and that the metadata fields are within bounds and internally consistent.
155 As such, we cannot catch all types of corruption that can occur within a block
156 as there may be certain limitations that operational state enforces of the
163 that it should see, and the IO completion process verifies that the metadata
201 structure. The latter occurs with metadata that already contains some of this
213 	  header that contains the magic number has other information in it as
236 The code ensures that the CRC is only checked if the filesystem has CRCs enabled
321 further, detecting corruptions that have occurred as the metadata has been
330 self-identifiers, but they are packed so that there are multiple objects per
333 identification of the buffer - that they contain inodes or dquots, and that