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

[LocutusOfBorg]

Uploaded in xenial new queue

** Changed in: btrfs-tools (Ubuntu Xenial)
       Status: Confirmed => Fix Committed

** Description changed:

+ [ 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.

-- 
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