[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-09-04。"],[],[],null,["# dfuse reference\n\nusage: `dfuse [OPTIONS] [mountpoint [pool container]]`\n\nOptions: \n\n -m --mountpoint=\u003cpath\u003e Mount point to use (deprecated, use positional argument)\n\n --pool=name pool UUID/label\n --container=name container UUID/label\n --path=\u003cpath\u003e Path to load UNS pool/container data\n --sys-name=STR DAOS system name context for servers\n\n -S --singlethread Single threaded\n -t --thread-count=count Total number of threads to use\n -e --eq-count=count Number of event queues to use\n -f --foreground Run in foreground\n --enable-caching Enable all caching (default)\n --enable-wb-cache Use write-back cache rather than write-through (default)\n --disable-caching Disable all caching\n --disable-wb-cache Use write-through rather than write-back cache\n -o options mount style options string\n\n --multi-user Run dfuse in multi user mode\n\n -h --help Show this help\n -v --version Show version\n\ndfuse performs a user space mount of a DAOS POSIX container at the mountpoint\ndirectory that is specified as the first positional argument. This directory\nhas to exist and has to be accessible to the user, or the mount will fail.\nAlternatively, the mountpoint directory can also be specified with the `-m` or\n`--mountpoint=` option but this usage is deprecated.\n\nThe DAOS pool and container can be specified in several different ways. Only\none way of specifying the pool and container should be used:\n\n- The DAOS pool and container can be explicitly specified on the command line as positional arguments, using either UUIDs or labels. This is the most common way to use dfuse to mount a POSIX container.\n- The DAOS pool and container can be explicitly specified on the command line using the `--pool` and `--container` options, with either UUIDs or labels. This usage is deprecated in favor of using positional arguments.\n- When the `--path` option is used, DAOS namespace attributes are loaded from that filesystem path, including the DAOS pool and container information.\n- When the `--path` option is not used, then the mountpoint directory will also be checked and DAOS namespace attributes will be loaded from there if present.\n- When using the `-o` mount option string, `pool=` and `container=` keys in the mount option string identify the DAOS pool and container.\n- When the pool and container are not specified through any of these methods,\n dfuse will construct filesystem pathnames under the mountpoint by using the\n pool and container UUIDs (not labels) of *all* pools and POSIX containers to\n which the user running dfuse has access as pathname components.\n\n - A path to a POSIX container that is mounted this way can be traversed to access the root of that container, for example by changing directory to `/mountpoint/pool_uuid/cont_uuid/`.\n - However, listing the /mountpoint/ directory is not supported and will not show the pool UUIDs that are mounted there.\n - Similarly, while the user can change directory into a `/mountpoint/pool_uuid/` directory, listing that directory is not supported and will not show the container UUIDs that are mounted there.\n - Running `fusermount3 -u /mountpoint` will unmount *all* POSIX containers that have been mounted this way, as well as the `/mountpoint/pool_uuid/` directories.\n\nThreading and resource usage:\n\ndfuse has two types of threads: fuse threads which accept and process requests\nfrom the kernel, and progress threads which complete asynchronous read/write\noperations.\n\nEach asynchronous progress thread uses one DAOS event queue to consume\nadditional network resources. As all metadata operations are blocking, the\nlevel of concurrency in dfuse is limited by the number of fuse threads.\n\nBy default, the total thread count is one per available core to allow maximum\nthroughput. If hyperthreading is enabled, then one thread per hyperthread core\nis used. This can be modified in two ways: Reducing the number of available\ncores by running dfuse in a cpuset via `numactl` or similar tools,\nor by using the `--thread-count`, `--eq-count` or `--singlethread` options:\n\n- The `--thread-count` option controls the total number of threads.\n- Increasing the `--eq-count` option at a fixed `--thread-count` will reduce the number of fuse threads accordingly. The default value for `--eq-count` is `1`.\n- The `--singlethread` mode will use one thread for handling fuse requests and a second thread for a single event queue, for a total of two threads.\n\nIf dfuse is running in background mode (the default unless launched via mpirun)\nthen it will stay in the foreground until the mount is registered with the\nkernel to allow appropriate error reporting.\n\nThe `-o` option can be used to run dfuse via fstab or similar and accepts\nstandard mount options. This will be treated as a comma separated list of\nkey=value pairs, and dfuse will use `pool=` and `container=` keys from this\nstring.\n\nCaching is on by default. The caching behavior for a dfuse mount can be\ncontrolled by command line options. Further caching controls can be set on a\nper-container basis through container attributes.\n\n- If the `--disable-caching` option is used then no caching will be performed, and the container attributes are not used. The default is `--enable-caching`.\n- If `--disable-wb-cache` is used then the write operations for the whole mount are performed in write-through mode, and the container attributes are still used. The default is `--enable-wb-cache`.\n- If `--disable-caching` and `--enable-wb-cache` are both specified, the `--enable-wb-cache` option is ignored and no caching is performed."]]