All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Cc: dsterba@suse.com
Subject: [PATCH 0/5 v3] btrfs-progs: recover from failed metadata_uuid port kernel
Date: Fri, 25 Aug 2023 22:47:46 +0800	[thread overview]
Message-ID: <cover.1692963810.git.anand.jain@oracle.com> (raw)

The earlier revision, v2, of this patchset consisted of 16 patches, out of
which 12 have already been merged into the devel branch.

 v2: https://patchwork.kernel.org/project/linux-btrfs/list/?series=776027

This current patchset contains the remaining unmerged patches and
addresses the reported bug:

 bug report: https://github.com/kdave/btrfs-progs/actions/runs/5956097489/job/16156138260

In v3 of this patchset, btrfs_fs_devices::inconsistent_super variable
added, which helps determine whether all the devices in the fs_devices
share the same fsid and metadata_uuid.

Anand Jain (5):
  btrfs-progs: cleanup duplicate check metadata_uuid flag
  btrfs-progs: tune use the latest bdev in fs_devices for super_copy
  btrfs-progs: add support to fix superblock with CHANGING_FSID_V2 flag
  btrfs-progs: recover from the failed btrfstune -m|M
  btrfs-progs: test btrfstune -m|M ability to fix previous failures

 kernel-shared/volumes.c                    | 193 +++++++++++++++++++--
 kernel-shared/volumes.h                    |   1 +
 tests/misc-tests/034-metadata-uuid/test.sh |  70 ++++++--
 tune/change-metadata-uuid.c                |  48 ++++-
 tune/change-uuid.c                         |   4 +-
 tune/main.c                                |   6 +-
 tune/tune.h                                |   2 -
 7 files changed, 281 insertions(+), 43 deletions(-)

-- 
2.31.1


             reply	other threads:[~2023-08-25 14:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25 14:47 Anand Jain [this message]
2023-08-25 14:47 ` [PATCH 1/5] btrfs-progs: cleanup duplicate check metadata_uuid flag Anand Jain
2023-08-28 15:28   ` David Sterba
2023-08-25 14:47 ` [PATCH 2/5] btrfs-progs: tune use the latest bdev in fs_devices for super_copy Anand Jain
2023-08-28 15:27   ` David Sterba
2023-08-28 22:43     ` Anand Jain
2023-08-25 14:47 ` [PATCH 3/5] btrfs-progs: add support to fix superblock with CHANGING_FSID_V2 flag Anand Jain
2023-08-25 14:47 ` [PATCH 4/5] btrfs-progs: recover from the failed btrfstune -m|M Anand Jain
2023-08-25 14:47 ` [PATCH 5/5] btrfs-progs: test btrfstune -m|M ability to fix previous failures Anand Jain
2023-08-28 15:31 ` [PATCH 0/5 v3] btrfs-progs: recover from failed metadata_uuid port kernel 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.1692963810.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.