Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Boris Burkov <boris@bur.io>
To: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: [PATCH 0/2] btrfs-progs: forget removed devices
Date: Thu, 29 Feb 2024 10:36:53 -0800	[thread overview]
Message-ID: <cover.1709231441.git.boris@bur.io> (raw)

To fix bugs in multi-dev filesystems not handling a devt changing under
them when a device gets destroyed and re-created with a different devt,
we need to forget devices as they get removed.

Modify scan -u to take advantage of the kernel taking unvalidated block
dev names and modify udev to invoke this scan -u on device remove.

Boris Burkov (2):
  btrfs-progs: allow btrfs device scan -u on dead dev
  btrfs-progs: add udev rule to forget removed device

 64-btrfs-rm.rules | 7 +++++++
 Makefile          | 2 +-
 cmds/device.c     | 2 +-
 3 files changed, 9 insertions(+), 2 deletions(-)
 create mode 100644 64-btrfs-rm.rules

-- 
2.43.0


             reply	other threads:[~2024-02-29 18:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-29 18:36 Boris Burkov [this message]
2024-02-29 18:36 ` [PATCH 1/2] btrfs-progs: allow btrfs device scan -u on dead dev Boris Burkov
2024-02-29 18:36 ` [PATCH 2/2] btrfs-progs: add udev rule to forget removed device Boris Burkov
2024-02-29 19:53   ` David Sterba
2024-02-29 20:34     ` Boris Burkov
2024-03-01  2:31 ` [PATCH 0/2] btrfs-progs: forget removed devices Anand Jain
2024-03-01 11:54   ` David Sterba
2024-03-01 15:44     ` Boris Burkov
2024-03-04 18:07       ` David Sterba
2024-03-04 21:27         ` Boris Burkov

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.1709231441.git.boris@bur.io \
    --to=boris@bur.io \
    --cc=kernel-team@fb.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