Lines Matching full:verification

12 scalability, but of verification of the filesystem structure. Scalabilty of the
15 is this very scalability that causes the verification problem.
50 verification of metadata values, looking for values that are in range (and hence
51 not detected by automated verification checks) but are not correct. Finding and
76 self identifying and we can do much more expansive automated verification of the
84 contain, a large amount of the manual verification work can be skipped.
129 present that the run-time verification is not detecting.
156 The verification is completely stateless - it is done independently of the
166 For read verification, the caller needs to specify the expected type of metadata
168 object matches what was expected. If the verification process fails, then it
171 verification error it can do so by catching the EFSCORRUPTED error value. If we
175 The first step in read verification is checking the magic number and determining
182 Write verification is the opposite of the read verification - first the object
267 	    /* object specific verification checks here */
292 	    /* object specific verification checks here */
336 verification and CRC calculations. The per-buffer verifiers simply perform basic
339 verification checks are done when each inode is read from or written back to the
344 example, inode read verification is done in xfs_inode_from_disk() when the inode