Lines Matching refs:parent
70 Secondary metadata (e.g. reverse mapping and directory parent pointers) support
431 - Directory parent pointers
571 mapping and directory parent pointers are no exception.
1255 - If there's a parent node block, do the keys listed for this block match the
1423 back to the parent?
2501 to compute the relevant keys and write them into the parent node::
3403 in a well-known order: parent → child when updating the directory tree, and
3437 Consider the directory parent pointer repair code as an example.
3439 parent directory, and that the parent directory contains exactly one dirent
3447 if the scanner fails to lock a parent, it can drop and relock both the child
3448 and the prospective parent.
3714 directory's parent link count is bumped because the root directory's dotdot
3717 2. If the entry is a dotdot entry of a subdirectory, the parent's backref
3720 3. If the entry is neither a dot nor a dotdot entry, the target file's parent
3723 4. If the target is a subdirectory, the parent's child link count is bumped.
3726 with the live update hooks is that the scan cursor tracks which *parent*
3732 entries affect the parent's link count.
4384 Damaged files and directories are zapped, and files with no parent are
4401 1. Find the parent of the directory.
4403 parent has a child entry pointing back to the directory being repaired.
4458 A parent pointer is a piece of file metadata that enables a user to locate the
4459 file's parent directory without having to traverse the directory tree from the
4464 The parent pointer feature, however, makes total directory reconstruction
4467 XFS parent pointers include the dirent name and location of the entry within
4468 the parent directory.
4472 each dirent also contains a parent pointer pointing back to the dirent.
4473 Likewise, each parent pointer can be checked by ensuring that the target of
4474 each parent pointer is a directory and that it contains a dirent matching
4475 the parent pointer.
4478 **Note**: The ondisk format of parent pointers is not yet finalized.
4483 | Directory parent pointers were first proposed as an XFS feature more |
4485 | Each link from a parent directory to a child file is mirrored with an |
4487 | parent directory. |
4502 | in the parent, so the SGI parent pointer implementation cannot be |
4506 | that parent pointer attribute creation is likely to fail at some |
4509 | The original parent pointer design was too unstable for something like |
4516 | commit a dirent update and a parent pointer update in the same |
4536 3. For each parent pointer found in each file scanned, decide if the parent
4562 7. Update the dirent position field of parent pointers as necessary.
4567 `parent pointers directory repair
4577 sufficient to find the entry in the parent.
4586 dabtree, though this would have to be performed with the parent directory
4589 3. Same as above, but remove the old parent pointer entry and add a new one
4604 Discussion is ongoing under the `parent pointers patch deluge
4610 Online reconstruction of a file's parent pointer information works similarly to
4614 an `xfblob<xfblob>` for storing parent pointer names, and an xfarray for
4615 stashing parent pointer updates.
4624 a. Stash an addpptr entry for this parent pointer in the xfblob and xfarray
4630 4. For each live directory update received via the hook, decide if the parent
4636 We cannot write parent pointers directly to the temporary file because
4639 to apply the stashed parent pointer updates to the temporary file.
4641 5. Copy all non-parent pointer extended attributes to the temporary file.
4650 `parent pointers repair
4651 <https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git/log/?h=pptrs-online-parent-re…
4657 Examining parent pointers in offline repair works differently because corrupt
4677 1. Scan the inode for parent pointers.
4700 of the parent pointer if necessary.
4705 `offline parent pointers repair
4709 Rebuilding directories from parent pointers in offline repair is very
4718 2. The next pass records parent pointers pointing to the directories noted
4728 Use the parent pointer information recorded during step 2 to reconstruct
4746 Without parent pointers, the directory parent pointer online scrub code can
4747 detect a dotdot entry pointing to a parent directory that doesn't have a link
4752 With parent pointers, directories can be rebuilt by scanning parent pointers
4753 and parent pointers can be rebuilt by scanning directories.
5104 For media errors in blocks owned by files, parent pointers can be used to