Lines Matching refs:object

60 metadata object contains some form of unique identifier in a well known
62 hence parse and verify the metadata object. IF we can't independently identify
63 the type of metadata in the object, then the metadata doesn't describe itself
73 metadata object at runtime, during forensic analysis or repair.
105 object, we don't know what inode it belongs to and hence have to walk the entire
109 owner field in the metadata object, we can immediately do top down validation to
115 contents of the owner field are determined by the type of metadata object we are
127 For example, we can determine whether a metadata object is supposed to be free
130 compared to when the metadata object itself was last written.  If the free space
131 block is more recent than the object and the object's owner, then there is a
164 object matches what was expected. If the verification process fails, then it
165 marks the object being read as EFSCORRUPTED. The caller needs to catch this
173 compared against the value stored in the object itself. Once this is validated,
175 object specific metadata validation. If any of these checks fail, then the
178 Write verification is the opposite of the read verification - first the object
180 modification made to the object, After this, we calculate the CRC and insert it
181 into the object. Once this is done the write IO is allowed to continue. If any
194         __be64  owner;		/* parent object */
263 	/* object specific verification checks here */
288 	/* object specific verification checks here */
329 Inodes and dquots are special snowflakes. They have per-object CRC and
331 buffer. Hence we do not use per-buffer verifiers to do the work of per-object