From: Anand Jain <anand.jain@oracle.com>
To: Jonas Zeiger <jonas.zeiger@talpidae.net>, linux-btrfs@vger.kernel.org
Subject: Re: Detecting new partitions fails after "btrfs device scan --forget"
Date: Mon, 14 Sep 2020 08:36:16 +0800 [thread overview]
Message-ID: <40e2315e-e60e-6161-ceb7-acd8b8a4e4a0@oracle.com> (raw)
In-Reply-To: <1ab4e230fe413c033b195bbd0f7e1db0@talpidae.net>
> /dev/sda have been
> written, but we have been unable to inform the kernel of the change,
> probably because it/they are in use. As a result, the old partition(s)
> will remain in use. You should reboot now before making further changes.
>
> The partitions do not become visible so the deployment can't continue.
The forget subcommand does not touch the mounted device, and it frees
only the unmounted or unopened btrfs devices from its kernel memory.
Now the error seems to be about the device being kept open. Can you find
out who did not close it?
next prev parent reply other threads:[~2020-09-14 0:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-13 18:47 Detecting new partitions fails after "btrfs device scan --forget" Jonas Zeiger
2020-09-14 0:36 ` Anand Jain [this message]
[not found] ` <e8bdb0c13f5f91b90e75b1a218ded2cb@talpidae.net>
2020-09-18 11:05 ` Jonas Zeiger
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=40e2315e-e60e-6161-ceb7-acd8b8a4e4a0@oracle.com \
--to=anand.jain@oracle.com \
--cc=jonas.zeiger@talpidae.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