Lines Matching full:verification

11 scalability, but of verification of the filesystem structure. Scalabilty of the
14 is this very scalability that causes the verification problem.
49 verification of metadata values, looking for values that are in range (and hence
50 not detected by automated verification checks) but are not correct. Finding and
75 self identifying and we can do much more expansive automated verification of the
83 contain, a large amount of the manual verification work can be skipped.
128 present that the run-time verification is not detecting.
155 The verification is completely stateless - it is done independently of the
165 For read verification, the caller needs to specify the expected type of metadata
167 object matches what was expected. If the verification process fails, then it
170 verification error it can do so by catching the EFSCORRUPTED error value. If we
174 The first step in read verification is checking the magic number and determining
181 Write verification is the opposite of the read verification - first the object
266 	    /* object specific verification checks here */
291 	    /* object specific verification checks here */
335 verification and CRC calculations. The per-buffer verifiers simply perform basic
338 verification checks are done when each inode is read from or written back to the
343 example, inode read verification is done in xfs_inode_from_disk() when the inode