[Bug 1694891] Re: All btrfs-tools commands need a quiet option for scripting

[LocutusOfBorg]

The quiet mode is now there!
usage: btrfs send [-ve] [-p <parent>] [-c <clone-src>] [-f <outfile>] <subvol> [<subvol>...]

    Send the subvolume(s) to stdout.

    Sends the subvolume(s) specified by <subvol> to stdout.
    By default, this will send the whole subvolume. To do an incremental
    send, use '-p <parent>'. If you want to allow btrfs to clone from
    any additional local snapshots, use '-c <clone-src>' (multiple times
    where applicable). You must not specify clone sources unless you
    guarantee that these snapshots are exactly in the same state on both
    sides, the sender and the receiver. It is allowed to omit the
    '-p <parent>' option when '-c <clone-src>' options are given, in
    which case 'btrfs send' will determine a suitable parent among the
    clone sources itself.
    

    -e               If sending multiple subvols at once, use the new
                     format and omit the end-cmd between the subvols.
    -p <parent>      Send an incremental stream from <parent> to
                     <subvol>.
    -c <clone-src>   Use this snapshot as a clone source for an 
                     incremental send (multiple allowed)
    -f <outfile>     Output is normally written to stdout. To write to
                     a file, use this option. An alternative would be to
                     use pipes.
    --no-data        send in NO_FILE_DATA mode, Note: the output stream
                     does not contain any file data and thus cannot be used
                     to transfer changes. This mode is faster and useful to
                     show the differences in metadata.
    -v|--verbose     enable verbose output to stderr, each occurrence of
                     this option increases verbosity
    -q|--quiet       suppress all messages, except errors


** Tags removed: verification-needed
** Tags added: verification-done-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to btrfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1694891

Title:
  All btrfs-tools commands need a quiet option for scripting

Status in btrfs-tools package in Ubuntu:
  Fix Released
Status in btrfs-tools source package in Xenial:
  Fix Committed
Status in btrfs-tools source package in Yakkety:
  Fix Released
Status in btrfs-tools source package in Zesty:
  Fix Released
Status in btrfs-tools source package in Artful:
  Fix Released

Bug description:
  [ Impact ]

  by default btrfs spams a lot of messages on stderr, and has no "quiet"
  option to avoid that

  [ Test Case ]
  * Use it for a while and look at stderr messages

  [ Regression potential ]
  * none, the default behaviour won't change

  [ Other info ]
  * this is fixed in yakkety+ releases, only xenial and older are affected

  Btrfs send and receive are noisy on stderr by default (messages like
  "At subvol foo"). It'd be great to get an option to only print there
  if there is an error condition. I assume there are other commands
  which do the same.

  See the patched version that quiets send but not receive. (I didn't realise receive was also noisy when requesting the backport.)
  https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2017-May/017455.html
  https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+packages

  Many scripts/cron wrappers check for output on stderr in order to
  notify when warnings/errors occur. There should be a way to avoid
  triggering such notifications when btrfs commands are successful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/btrfs-tools/+bug/1694891/+subscriptions