borg-umount(1)
π NAME π
okay so bestie, <pink>borg-umount</pink> β it un-mounts the FUSE filesystem. that's it. that's the whole job. she's a closer, not an opener π
β¨ SYNOPSIS β¨
borg [common options] umount [options] MOUNTPOINT
π¦ DESCRIPTION π¦
so like. you mounted something with borg mount and now you want it gone?? valid. <hotpink>borg-umount</hotpink> unmounts a FUSE filesystem that was mounted with borg mount. bye felicia π
and here's the tea: she's a <purple>convenience wrapper</purple> β meaning she doesn't do the heavy lifting herself, she just calls the platform-specific shell command for you. usually that's either umount or fusermount -u. so she's basically the friend who makes the phone call for you bc you're too anxious π iconic behavior honestly.
π₯ OPTIONS π₯
head over to borg-common(1) for the common options of Borg commands, bestie β that's where the shared stuff lives π«Ά
arguments
MOUNTPOINTβ the mountpoint of the filesystem you wanna umount. like, the place it's mounted at. that's the one you need to tell her π
πΈ EXAMPLES πΈ
okay these are so good, let's go one by one:
# Mounting the repository shows all archives.
# Archives are loaded lazily, expect some delay when navigating to an archive
# for the first time.
$ borg mount /path/to/repo /tmp/mymountpoint
$ ls /tmp/mymountpoint
root-2016-02-14 root-2016-02-15
$ borg umount /tmp/mymountpoint
see how the repo mount shows all archives? and heads up no cap β archives are loaded lazily, so expect some delay when you navigate into an archive for the first time. she's not being slow, she's just vibing on demand β¨
# Mounting a specific archive is possible as well.
$ borg mount /path/to/repo::root-2016-02-15 /tmp/mymountpoint
$ ls /tmp/mymountpoint
bin boot etc home lib lib64 lost+found media mnt opt
root sbin srv tmp usr var
$ borg umount /tmp/mymountpoint
you can also mount one specific archive instead of the whole repo. look at that classic root filesystem layout, she ate π
# The "versions view" merges all archives in the repository
# and provides a versioned view on files.
$ borg mount -o versions /path/to/repo /tmp/mymountpoint
$ ls -l /tmp/mymountpoint/home/user/doc.txt/
total 24
-rw-rw-r-- 1 user group 12357 Aug 26 21:19 doc.cda00bc9.txt
-rw-rw-r-- 1 user group 12204 Aug 26 21:04 doc.fa760f28.txt
$ borg umount /tmp/mymountpoint
the "versions view" merges all the archives in the repository and gives you a versioned view on your files. every version of doc.txt just chilling side by side with its little hash names. so satisfying π
# Archive filters are supported.
# These are especially handy for the "versions view",
# which does not support lazy processing of archives.
$ borg mount -o versions --glob-archives '*-my-home' --last 10 /path/to/repo /tmp/mymountpoint
archive filters are supported! and they're especially handy for the "versions view" β bc that view does not support lazy processing of archives. so filter it down, bestie π
# Exclusion options are supported.
# These can speed up mounting and lower memory needs significantly.
$ borg mount /path/to/repo /tmp/mymountpoint only/that/path
$ borg mount --exclude '...' /path/to/repo /tmp/mymountpoint
exclusion options?? supported. and they can speed up mounting AND lower memory needs significantly. that's a glow-up fr fr π₯
# When using BORG_REPO env var, use :: as positional argument:
export BORG_REPO=/path/to/repo
# Mount the whole repo:
borg mount :: /tmp/mymountpoint
# Mount some specific archive:
borg mount ::root-2016-02-15 /tmp/mymountpoint
when you're using the <cyan>BORG_REPO</cyan> env var, use :: as the positional argument. lowkey genius π§
π borgfs π
$ echo '/mnt/backup /tmp/myrepo fuse.borgfs defaults,noauto 0 0' >> /etc/fstab
$ echo '/mnt/backup::root-2016-02-15 /tmp/myarchive fuse.borgfs defaults,noauto 0 0' >> /etc/fstab
$ mount /tmp/myrepo
$ mount /tmp/myarchive
$ ls /tmp/myrepo
root-2016-02-01 root-2016-02-15
$ ls /tmp/myarchive
bin boot etc home lib lib64 lost+found media mnt opt root sbin srv tmp usr var
Note: <hotpink>borgfs</hotpink> will be automatically provided if you used a distribution package or pip to install Borg. users of the standalone binary will have to manually create a symlink (see pyinstaller-binary). don't skip this step, she will not spawn herself π
not me reminding you that the standalone binary girlies gotta make that symlink by hand. it's giving DIY energy π
π SEE ALSO π
π Author π
The Borg Collective
okay that's the whole page, bestie!! this was borg-umount(1) from the borg backup tool, and the version/date on the tin is <rainbow>2026-07-18</rainbow>. now go unmount something, you've got this π«Άβ¨
π¦ where this page comes from
- alpine 3.24: borgbackup-doc 1.4.5-r0 Β· BSD-3-Clause
- arch rolling: borg 1.4.5-1 Β· BSD
- ubuntu stonking: borgbackup 1.4.5-1 Β· BSD-3-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms