public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org, dsterba@suse.com
Subject: [PATCH 0/2] btrfs: migrate tracking read blocks from fs_devices to
Date: Thu,  9 Jan 2025 05:01:34 +0800	[thread overview]
Message-ID: <cover.1736369474.git.anand.jain@oracle.com> (raw)

David reported btrfs/161 failing during sprouted filesystem unmount.
Bisected to commit 49136a74162e ("btrfs: add tracking of read blocks
for read policy"). Now, tracking is moved from `fs_devices` to `fs_info`.

Tested to be working fine.

-----
FSTYP         -- btrfs
PLATFORM      -- Linux/aarch64 local 6.13.0-rc6+ #45 SMP PREEMPT_DYNAMIC Thu Jan  9 04:04:07 +08 2025
MKFS_OPTIONS  -- /dev/sdb
MOUNT_OPTIONS -- -o context=system_u:object_r:root_t:s0 /dev/sdb /mnt/scratch

btrfs/161 0s ...  0s
Ran: btrfs/161
Passed all 1 tests
------

Patches should be folded into their respective commits. Thx.

Anand Jain (2):
  fixup: btrfs: add tracking of read blocks for read policy
  fixup: btrfs: introduce RAID1 round-robin read balancing

 fs/btrfs/bio.c     |  2 +-
 fs/btrfs/disk-io.c |  5 +++++
 fs/btrfs/fs.h      |  3 +++
 fs/btrfs/volumes.c | 17 ++++++-----------
 fs/btrfs/volumes.h |  3 ---
 5 files changed, 15 insertions(+), 15 deletions(-)

-- 
2.47.0


             reply	other threads:[~2025-01-08 21:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-08 21:01 Anand Jain [this message]
2025-01-08 21:01 ` [PATCH 1/2] fixup: btrfs: add tracking of read blocks for read policy Anand Jain
2025-01-08 21:01 ` [PATCH 2/2] fixup: btrfs: introduce RAID1 round-robin read balancing Anand Jain
2025-01-09 10:17 ` [PATCH 0/2] btrfs: migrate tracking read blocks from fs_devices to 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=cover.1736369474.git.anand.jain@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=dsterba@suse.com \
    --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