public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: dsterba@suse.cz
Cc: linux-btrfs@vger.kernel.org, dsterba@suse.com,
	aromosan@gmail.com, bernd.feige@gmx.net
Subject: Re: [PATCH] btrfs: do not skip re-registration for the mounted device
Date: Tue, 13 Feb 2024 06:05:53 +0530	[thread overview]
Message-ID: <8b5c55e0-c9f5-496f-a8ff-cc8eadf64840@oracle.com> (raw)
In-Reply-To: <20240212145931.GD355@twin.jikos.cz>



On 2/12/24 20:29, David Sterba wrote:
> On Mon, Feb 05, 2024 at 07:45:05PM +0800, Anand Jain wrote:
>> We skip device registration for a single device. However, we do not do
>> that if the device is already mounted, as it might be coming in again
>> for scanning a different path.
>>
>> This patch is lightly tested; for verification if it fixes.
>>
>> Signed-off-by: Anand Jain <anand.jain@oracle.com>
>> ---

>> I still have some unknowns about the problem. Pls test if this fixes
>> the problem.

It is a mystery- we didn't see
    "BTRFS: skip registering single non-seed device %s\n",
in the kernel messages.

Do you have any clue?

> Seems that we have that tested by some reportes, I checked it in my VM
> setup that it works (fstests and grub2-probe) so let's add it to
> for-next. Please use the changelog from my patch that describes the
> problem and then add description of how you fixed it. Thanks.

Thxs for the verification. I'll revise, send out.

Thx, Anand

  reply	other threads:[~2024-02-13  0:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-05 11:45 [PATCH] btrfs: do not skip re-registration for the mounted device Anand Jain
2024-02-05 12:57 ` David Sterba
2024-02-07  2:38   ` Anand Jain
2024-02-07 18:08     ` Anand Jain
     [not found]       ` <CAKLYge+9ngrW-1EffUhyU1y13MzgP33osNDi3D6y6UVW6poJZA@mail.gmail.com>
2024-02-08  2:23         ` Anand Jain
2024-02-08 12:35           ` Alex Romosan
2024-02-08 17:22             ` Anand Jain
2024-02-08 19:45               ` Alex Romosan
2024-02-08 20:04               ` Alex Romosan
2024-02-09  8:11                 ` Anand Jain
2024-02-09 15:27                   ` Dr. Bernd Feige
2024-02-12 14:59 ` David Sterba
2024-02-13  0:35   ` Anand Jain [this message]
2024-02-13 19:38     ` 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=8b5c55e0-c9f5-496f-a8ff-cc8eadf64840@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=aromosan@gmail.com \
    --cc=bernd.feige@gmx.net \
    --cc=dsterba@suse.com \
    --cc=dsterba@suse.cz \
    --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