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 &lt;path&gt;. 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: lsbtr requires root privileges to run correctly. If that's not it for you, consider the btrfs-progs-sudo or btrfs-progs-btrbk backends instead β€” both of them let you run lsbtr as a regular user 🫢. Peep the configuration option backend in btrbk.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 the btrbk version. 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-separated key="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 to raw, it prints space-separated key="value" pairs (machine readable, same deal as above).
    • If you set it to col:, it prints only the &lt;columns&gt; 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 :RALIGN are right-aligned. They're standing on the right side of history ✨
  • -v, --verbose β€” increase the level of verbosity. Spill more tea β˜•
  • -c, --config <file> β€” read the configuration from &lt;file&gt;. Choose your own adventure πŸ“‚
  • --override <config_option>=<value> β€” override a configuration option &lt;config_option&gt; with &lt;value&gt;. 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 in btrbk.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