Lines Matching refs:t

749 …      6. Both repair tools (``xfs_scrub`` and then ``xfs_repair`` if online repair doesn't succeed)
791   filesystem doesn't cause problems.
793   force-repairing the whole filesystem doesn't cause problems.
945 that doesn't belong to the filesystem, and the fourth component enables the
1248    - If these aren't file data blocks, are none of the blocks claimed as space
1662 Again, this generally isn't a problem because XFS orders its deferred work
1781 replace a static branch to hook code with ``nop`` sleds when online fsck isn't
1855 in a place that doesn't require the correct operation of the filesystem.
1857 Kernel memory isn't suitable because:
1876 to store intermediate data that doesn't need to be in memory at all times, so
2067 know that there aren't any.
2315 log transactions back into the filesystem, and certainly won't exist during
2663 Single-owner file blocks aren't recorded in either the free space or the
2704   - While the bag isn't empty:
3074 incore counter and give back whatever they don't use at commit time.
3370 This isn't much of a problem for ``iget`` since it can operate in the context
3632 Like most online fsck functions, online quotacheck can't write to regular
4087 the mappings aren't necessarily aligned.
4446 Unfortunately, the current dentry cache design doesn't provide a means to walk
4747 detect a dotdot entry pointing to a parent directory that doesn't have a link
4749 that isn't pointed to by any directory in the filesystem.
4904 This doesn't completely solve the balancing problem, but reduces it enough to
5224 Given that the scrub codebase has helpers to detect fatal signals, it shouldn't
5287 That problem isn't totally insurmountable: create an inode remapping table
5290 The trouble is, the kernel can't do anything about open files, since it cannot