From: Christoph Anton Mitterer <calestyo@scientia.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: defrag: add under utilized extent to defrag target list
Date: Mon, 05 Feb 2024 06:39:31 +0100 [thread overview]
Message-ID: <c6fcbd44c7ecb06c92f6062e6843a1d106b5799a.camel@scientia.org> (raw)
In-Reply-To: <2c2fac36b67c97c9955eb24a97c6f3c09d21c7ff.1704440000.git.wqu@suse.com>
Hey there.
Is that patch still under consideration?
The filesystems on my 6.1 kernel regularly run full because of these IO
patterns... and AFAICS the patch hasn't been merged to master or
backported to the stables yet.
Any ideas how to proceed?
I mean if btrfs just break with that specific kind of IO patterns and
there will be no fix,... fine,... but then please tell so that I can
witch to something else for that use case :-)
Cheers,
Chris.
next prev parent reply other threads:[~2024-02-05 5:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 7:33 [PATCH] btrfs: defrag: add under utilized extent to defrag target list Qu Wenruo
2024-01-05 16:45 ` Andrei Borzenkov
2024-01-05 20:11 ` Qu Wenruo
2024-01-09 14:55 ` Filipe Manana
2024-01-09 16:12 ` Filipe Manana
2024-01-09 21:04 ` Qu Wenruo
2024-01-09 21:57 ` Christoph Anton Mitterer
2024-01-09 22:17 ` Qu Wenruo
2024-01-10 17:09 ` David Sterba
2024-01-11 6:24 ` Qu Wenruo
2024-01-12 15:58 ` David Sterba
2024-01-13 3:17 ` Qu Wenruo
2024-01-13 8:05 ` Andrei Borzenkov
2024-01-13 8:32 ` Qu Wenruo
2024-01-13 3:47 ` Christoph Anton Mitterer
2024-02-05 5:39 ` Christoph Anton Mitterer [this message]
2024-02-05 5:42 ` Qu Wenruo
2024-04-20 4:30 ` Skirnir Torvaldsson
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=c6fcbd44c7ecb06c92f6062e6843a1d106b5799a.camel@scientia.org \
--to=calestyo@scientia.org \
--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