linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH DRAFT 0/6] btrfs-progs: partial support for WRITE_INTENT_BITMAP compat RO flag
Date: Wed, 15 Jun 2022 06:56:28 +0800	[thread overview]
Message-ID: <cover.1655247047.git.wqu@suse.com> (raw)

This is the btrfs-progs counter-part to add placeholder for
WRITE_INTENT_BITMAP compat RO flag.

The same as kernel, this will have two compat RO flags:

- EXTRA_SUPER_RESERVED
  To indicate exactly how many bytes are reserved at the beginning of
  each device.

  By default mkfs.btrfs will reserve another 1MiB in addition to the
  existing 1MiB.

  So that later write-intent-bitmap can utilize the extra space.
  (although write-intent-bitmap may only utilize at most 64KiB).

- WRITE_INTENT_BITMAP
  Just to indicate if we have write intent bitmap.

  Currently it doesn't do any real work (aka, just a place holder).

Thus the patchset is mostly for EXTRA_SUPER_RESERVED, including the
following part:

- Add the needed definition
- Add mkfs support
- Add print-tree support
- Add extra warning and solution for btrfsck
  For EXTRA_SUPER_RESERVED only, it's no different than the initial
  1MiB reservation, kernel can handle it without problem.

  The extra check support will just do warning, and at the end, output
  a solution (using balance with drange filter).

Qu Wenruo (6):
  btrfs-progs: introduce a new compat RO flag, EXTRA_SUPER_RESERVED
  btrfs-progs: mkfs: add support for extra-super-reserved runtime flag
  btrfs-progs: print-tree: remove duplicated definition for compat RO
    flags
  btrfs-progs: print-tree: support btrfs_super_block::reserved_bytes
  btrfs-progs: check: add extra warning for dev extents inside the
    reserved range
  btrfs-progs: introduce the experimental compat RO flag,
    WRITE_INTENT_BITMAP

 check/main.c               | 17 ++++++++++++++++
 check/mode-lowmem.c        | 22 +++++++++++++++++++++
 common/fsfeatures.c        | 19 ++++++++++++++++++
 common/fsfeatures.h        |  2 ++
 kernel-shared/ctree.h      | 40 ++++++++++++++++++++++++++++++++++++--
 kernel-shared/disk-io.c    | 18 +++++++++++++++++
 kernel-shared/print-tree.c | 11 ++++++++---
 kernel-shared/volumes.c    |  4 ++++
 mkfs/common.c              | 25 ++++++++++++++++++++++++
 mkfs/main.c                | 14 +++++++++++++
 10 files changed, 167 insertions(+), 5 deletions(-)

-- 
2.36.1


             reply	other threads:[~2022-06-14 22:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-14 22:56 Qu Wenruo [this message]
2022-06-14 22:56 ` [PATCH DRAFT 1/6] btrfs-progs: introduce a new compat RO flag, EXTRA_SUPER_RESERVED Qu Wenruo
2022-06-14 22:56 ` [PATCH DRAFT 2/6] btrfs-progs: mkfs: add support for extra-super-reserved runtime flag Qu Wenruo
2022-06-14 22:56 ` [PATCH DRAFT 3/6] btrfs-progs: print-tree: remove duplicated definition for compat RO flags Qu Wenruo
2022-06-14 22:56 ` [PATCH DRAFT 4/6] btrfs-progs: print-tree: support btrfs_super_block::reserved_bytes Qu Wenruo
2022-06-14 22:56 ` [PATCH DRAFT 5/6] btrfs-progs: check: add extra warning for dev extents inside the reserved range Qu Wenruo
2022-06-14 22:56 ` [PATCH DRAFT 6/6] btrfs-progs: introduce the experimental compat RO flag, WRITE_INTENT_BITMAP Qu Wenruo

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.1655247047.git.wqu@suse.com \
    --to=wqu@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;
as well as URLs for NNTP newsgroup(s).