123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263 |
- .. IMPORTANT: this file is auto-generated from borg's built-in help, do not edit!
- .. _borg_mount:
- borg mount
- ----------
- ::
- usage: borg mount [-h] [--critical] [--error] [--warning] [--info] [--debug]
- [--lock-wait N] [--show-rc] [--no-files-cache] [--umask M]
- [--remote-path PATH] [-f] [-o OPTIONS]
- REPOSITORY_OR_ARCHIVE MOUNTPOINT
-
- Mount archive or an entire repository as a FUSE filesystem
-
- positional arguments:
- REPOSITORY_OR_ARCHIVE
- repository/archive to mount
- MOUNTPOINT where to mount filesystem
-
- optional arguments:
- -h, --help show this help message and exit
- --critical work on log level CRITICAL
- --error work on log level ERROR
- --warning work on log level WARNING (default)
- --info, -v, --verbose
- work on log level INFO
- --debug work on log level DEBUG
- --lock-wait N wait for the lock, but max. N seconds (default: 1).
- --show-rc show/log the return code (rc)
- --no-files-cache do not load/update the file metadata cache used to
- detect unchanged files
- --umask M set umask to M (local and remote, default: 0077)
- --remote-path PATH set remote path to executable (default: "borg")
- -f, --foreground stay in foreground, do not daemonize
- -o OPTIONS Extra mount options
-
- Description
- ~~~~~~~~~~~
- This command mounts an archive as a FUSE filesystem. This can be useful for
- browsing an archive or restoring individual files. Unless the ``--foreground``
- option is given the command will run in the background until the filesystem
- is ``umounted``.
- The BORG_MOUNT_DATA_CACHE_ENTRIES environment variable is meant for advanced users
- to tweak the performance. It sets the number of cached data chunks; additional
- memory usage can be up to ~8 MiB times this number. The default is the number
- of CPU cores.
- For mount options, see the fuse(8) manual page. Additional mount options
- supported by borg:
- - allow_damaged_files: by default damaged files (where missing chunks were
- replaced with runs of zeros by borg check --repair) are not readable and
- return EIO (I/O error). Set this option to read such files.
- When the daemonized process receives a signal or crashes, it does not unmount.
- Unmounting in these cases could cause an active rsync or similar process
- to unintentionally delete data.
- When running in the foreground ^C/SIGINT unmounts cleanly, but other
- signals or crashes do not.
|