From: Roman Mamedov <rm@romanrm.net>
To: Lionel Bouton <lionel-subscription@bouton.name>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: [btrfs-progs] btrfs filesystem defragment now outputs processed filenames ?
Date: Mon, 17 Oct 2022 21:50:46 +0500 [thread overview]
Message-ID: <20221017215046.6e29e7bb@nvm> (raw)
In-Reply-To: <e1cf9a2c-71e7-0bb6-7926-1c5952de02f7@bouton.name>
On Mon, 17 Oct 2022 13:32:03 +0200
Lionel Bouton <lionel-subscription@bouton.name> wrote:
> This isn't a big problem and it is easily fixable in my scheduler but I
> was wondering if there is any plan to allow silencing it or should I
> just cleanup the ouput before forwarding it (I prefer to write any
> unexpected output in logs instead of ignoring everything) ?
If there wasn't a "--quiet", the usual approach would be to discard stdout and
log stderr; or log stdout, but log and mail stderr. So you only get notified
of any errors, and not the normal operation output. That's assuming btrfs
progs follow the good practice and designate printed messages accordingly
between these two (I did not check).
--
With respect,
Roman
next prev parent reply other threads:[~2022-10-17 16:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 11:32 [btrfs-progs] btrfs filesystem defragment now outputs processed filenames ? Lionel Bouton
2022-10-17 15:47 ` Patrik Lundquist
2022-10-17 16:38 ` Lionel Bouton
2022-10-17 16:50 ` Roman Mamedov [this message]
2022-11-11 15:47 ` David Sterba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221017215046.6e29e7bb@nvm \
--to=rm@romanrm.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=lionel-subscription@bouton.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).