linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lionel Bouton <lionel-subscription@bouton.name>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: [btrfs-progs] btrfs filesystem defragment now outputs processed filenames ?
Date: Mon, 17 Oct 2022 13:32:03 +0200	[thread overview]
Message-ID: <e1cf9a2c-71e7-0bb6-7926-1c5952de02f7@bouton.name> (raw)

Hi,

I just noticed a change in behavior for btrfs-progs (at least in 6.0-1 
on Arch Linux). It now outputs the filenames it defragments and I can't 
find a command line option to disable it.

I'm using a defragment scheduler which triggers file defragmentation 
file by file and even recently by offset and size in a file (to limit 
the IO load spikes that can happen when defragmenting large files on HDD 
and T/QLC SSD/NVME with small SLC buffers).
Currently the scheduler forwards the btrfs command's output to its own 
and it pollutes the logs with superfluous information (when 
defragmenting in 128MB chunks I get tens of log lines for multiple GB 
files).

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

Best regards,

Lionel


             reply	other threads:[~2022-10-17 11:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-17 11:32 Lionel Bouton [this message]
2022-10-17 15:47 ` [btrfs-progs] btrfs filesystem defragment now outputs processed filenames ? Patrik Lundquist
2022-10-17 16:38   ` Lionel Bouton
2022-10-17 16:50 ` Roman Mamedov
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=e1cf9a2c-71e7-0bb6-7926-1c5952de02f7@bouton.name \
    --to=lionel-subscription@bouton.name \
    --cc=linux-btrfs@vger.kernel.org \
    /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).