From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs-progs - failed btrfs replace on RAID1 seems to have left things in a wrong state
Date: Fri, 1 Dec 2017 20:37:38 +0000 (UTC) [thread overview]
Message-ID: <pan$10b1c$c01da1a$3a1f81da$cc066079@cox.net> (raw)
In-Reply-To: CAA7pwKOhxP=zLreSXoZfG5TzmiHhfAetVuqXxfz7a=KrkJXoQw@mail.gmail.com
Patrik Lundquist posted on Fri, 01 Dec 2017 10:29:43 +0100 as excerpted:
> On 1 December 2017 at 08:18, Duncan <1i5t5.duncan@cox.net> wrote:
>>
>> When udev sees a device it triggers
>> a btrfs device scan, which lets btrfs know which devices belong to which
>> individual btrfs. But once it associates a device with a particular
>> btrfs, there's nothing to unassociate it -- the only way to do that on
>> a running kernel is to successfully complete a btrfs device remove or
>> replacement... and your replace didn't complete due to error.
>>
>> Of course the other way to do it is to reboot, fresh kernel, fresh
>> btrfs state, and it learns again what devices go with which btrfs
>> when the appearing devices trigger the udev rule that triggers a
>> btrfs scan.
>
> Or reload the btrfs module.
Thanks. Yes. With a monolithic kernel I tend to forget about that (and
as I have a btrfs root it wouldn't be possible anyway), but indeed,
unloading/reloading the btrfs kernel module clears the btrfs device state
tracking as effectively as a reboot. Good point! =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2017-12-01 20:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 12:43 btrfs-progs - failed btrfs replace on RAID1 seems to have left things in a wrong state Eric Mesa
2017-12-01 7:18 ` Duncan
2017-12-01 9:29 ` Patrik Lundquist
2017-12-01 20:37 ` Duncan [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-12-01 12:08 Eric Mesa
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='pan$10b1c$c01da1a$3a1f81da$cc066079@cox.net' \
--to=1i5t5.duncan@cox.net \
--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).