Lines Matching refs:t

28 weren't the ultimate cause of a corruption event. It may take a few hours to a
45 is supposed to be. We can't even identify if it is the right place. Put simply,
46 you can't look at a single metadata block in isolation and say "yes, it is
59 of analysis. We can't protect against every possible type of error, but we can
66 hence parse and verify the metadata object. IF we can't independently identify
67 the type of metadata in the object, then the metadata doesn't describe itself
75 the metadata isn't self identifying. If it contains a new magic number, it is
109 object, we don't know what inode it belongs to and hence have to walk the entire
246 the case it can't, the code is structured as follows::
350 XXX: inode unlinked list modification doesn't recalculate the inode CRC! None of
352 log recovery. So, it's gone unnoticed until now. This won't matter immediately -