Lines Matching full:metadata
38 * Metadata Directory Tree
42 * deleting metadata inodes that live within a special metadata directory tree.
44 * This code does not manage the five existing metadata inodes: real time
45 * bitmap & summary; and the user, group, and quotas. All other metadata
48 * Callers wishing to create or hardlink a metadata inode must create an
51 * the update. Files in the metadata directory tree currently cannot be
54 * When the metadir feature is enabled, all metadata inodes must have the
55 * "metadata" inode flag set to prevent them from being exposed to the outside
58 * Callers must take the ILOCK of any inode in the metadata directory tree to
60 * or the MMAPLOCK since metadata inodes must not be exposed to user space.
75 * Given a parent directory @dp and a metadata inode path component @xname,
128 * Look up and read a metadata inode from the metadata directory. If the path
154 * Unlock and release resources after committing (or cancelling) a metadata
182 * Begin the process of creating a metadata file by allocating transactions
202 * If we ever need the ability to create rt metadata files on a in xfs_metadir_start_create()
228 * Create a metadata inode with the given @mode, and insert it into the
229 * metadata directory tree at the given @upd->path. The path up to the final
232 * The new metadata inode will be attached to the update structure @upd->ip,
317 * Begin the process of linking a metadata file by allocating transactions
363 * Link the metadata directory given by @path to the inode @upd->ip.
441 /* Create a metadata for the last component of the path. */