All btrfs-tools commands need a quiet option for scripting

Looks like it's on the horizon upstream:
https://bugzilla.kernel.org/show_bug.cgi?id=111421#c1

Maybe a prod from distro devs can help things along?

hello, does my ppa fix the issue for you? (the receive issue I mean)?

Can you please convert your bug into an SRU request if you want the patch be uploaded into the main archive.
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template

Subscribing xnox :)

Uploaded in xenial new queue

Hello Lucas, or anyone else affected,

Accepted btrfs-tools into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/btrfs-tools/4.4-1ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

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

old help menu
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.

    -v Enable verbose debug output. Each occurrence of
                     this option increases the verbose level more.
    -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.

This bug was fixed in the package btrfs-tools - 4.4-1ubuntu1

---------------
btrfs-tools (4.4-1ubuntu1) xenial; urgency=medium

  * debian/patches/09c052a8b4dcaa96fe5e6c28b12ce24729e827a4.patch:
    backport upstream commit to add new "quiet option" and prevent printing of
    messages on stderr (LP: #1694891)

 -- Gianfranco Costamagna <email address hidden> Wed, 14 Jun 2017 19:48:16 +0200

The verification of the Stable Release Update for btrfs-tools has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

I'm using btrfs-progs version 4.12-1

I found a -q option to btrfs send, but since there is no btrfs receive I still see this message:
At subvol XXX

Is there any way to avoid that output too?