LSBTR(1)
β¨ NAME β¨
lsbtr β bestie, it lists btrfs subvolumes π (this is the LSBTR(1) page from the Btrbk Manual, iykyk)
π¦ SYNOPSIS π¦
lsbtr [-h|--help] [--version]
[-l|--long] [-u|--uuid] [-1|--single-column] [--raw]
[--format <output-format>]
[-v|--verbose]
[-c|--config <file>]
[--override <config_option>=<value>]
[[--] <path>|<url>...]
πΈ DESCRIPTION πΈ
Okay so picture this: lsbtr lists btrfs subvolumes and their mount points that are visible by the file system below <path>. That's the whole vibe. π
It's part of btrbk β literally just a shortcut for btrbk ls β and it takes some global configuration options from btrbk.conf(5) if that file is present. No cap. π
π¨ Real talk though:lsbtrrequires root privileges to run correctly. If that's not it for you, consider thebtrfs-progs-sudoorbtrfs-progs-btrbkbackends instead β both of them let you runlsbtras a regular user π«Ά. Peep the configuration optionbackendinbtrbk.conf(5)for the details, bestie.
π OPTIONS π
-h,--helpβ prints the synopsis and a list of the commands. The "wait what do I type" button β¨--versionβ prints thebtrbkversion. Receipts only π-l,--longβ print output in long table format (and, extra, it also prints the subvolume path). More columns, more lore π-u,--uuidβ print the UUID table (that's the parent/received relations). Family tree but make it UUIDs π§¬-1,--single-columnβ print the path column only, delimited by newline. One column, zero chaos π--rawβ print space-separatedkey="value"pairs. Machine readable, so your scripts can eat π--format table|long|raw|col:[h:]<columns>β print output in the specified format. If you set it toraw, it prints space-separatedkey="value"pairs (machine readable, same deal as above).- If you set it to
col:, it prints only the <columns> you specified β that's a comma-separated list, bestie, don't forget the commas π - Header lines are omitted if the
h:modifier is present. No header, just vibes π - Columns prefixed with
-get collapsed if they're empty. Shy columns get to sit this one out π«Ά - Columns postfixed with
:RALIGNare right-aligned. They're standing on the right side of history β¨
- If you set it to
-v,--verboseβ increase the level of verbosity. Spill more tea β-c,--config <file>β read the configuration from <file>. Choose your own adventure π--override <config_option>=<value>β override a configuration option <config_option> with <value>. Main character energy: your value, your rules π
π FILES π
/etc/btrbk.conf,/etc/btrbk/btrbk.confβ the default configuration file. The file format and the configuration options are described over inbtrbk.conf(5). Go read it, it's giving documentation π
π₯ EXIT STATUS π₯
lsbtr returns the following error codes, and yes you will be checking them:
0β no problems occurred. Clean run, flawless, we love to see it β¨1β generic error code. It's giving "something happened, idk what" π2β parse error: this is when parsing command-line options or the configuration file goes sideways. Something you typed? Not it π255β script error. Big yikes territory π¨
π§ AVAILABILITY π§
Please refer to the btrbk project page https://digint.ch/btrbk/ for further details. That's the mothership, bestie πΈ
π SEE ALSO π
btrbk(1), btrbk.conf(5), btrfs(8)
The friend group. Go say hi π«Ά
π AUTHOR π
Axel Burri axel@tty0.ch β the icon who wrote this, we stan π
And that's the whole page, bestie!! πΈ This was Btrbk 0.32.7, dated 2026-07-19, and it's the LSBTR(1) manual β go forth and list those subvolumes, slay, periodt π β¨
π¦ where this page comes from
- arch rolling: btrbk 0.32.7-1 Β· GPL-3.0-or-later
- fedora 43: btrbk 0.32.7-1.fc43 Β· GPL-3.0-or-later
- fedora 44: btrbk 0.32.7-1.fc44 Β· GPL-3.0-or-later
- nixos 26.05: btrbk 0.32.7
- nixpkgs unstable: btrbk 0.32.7
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms