Lines Matching refs:Inode

364 - Inode records and indexes
1274 4. Inode btree records are cross-referenced as follows:
1285 5. Inode records are cross-referenced as follows:
2567 Case Study: Rebuilding the Inode Index
2999 Inode Record Repairs
3002 Inode records must be handled carefully, because they have both ondisk records
3174 Coordinated Inode Scans
3289 Inode Management
3324 1. Inode reference (``iget``).
3328 3. Inode ``IOLOCK`` (VFS ``i_rwsem``) lock to control file IO.
3330 4. Inode ``MMAPLOCK`` (page cache ``invalidate_lock``) lock for operations that
3342 9. Inode ``ILOCK`` for file metadata updates.
3406 Inode lock acquisition must be done carefully during a coordinated inode scan.
5018 f. Inode records depends on consistency within the inode metadata indices.
5055 Parallel Inode Scans