All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: Nikolay Borisov <nborisov@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 1/2] btrfs-progs: Ignore path device during device scan
Date: Wed, 29 Sep 2021 20:44:08 +0800	[thread overview]
Message-ID: <c2828ccd-80a2-a7c9-0282-bb58046375c3@oracle.com> (raw)
In-Reply-To: <42ce59f6-4458-5cf9-351e-7fa81d62ebf5@suse.com>



>>> flap means going up and down. The gist is that btrfs fi show would show
>>> the latest device being scanned, which in the case of multipath device
>>> could be any of the paths.

   But why the problem is only when a device flaps? Or it doesn't matter?

>>   Do you mean 'btrfs fi show' shows a device of the multi-path however,
>>   'btrfs fi show -m' shows the correct multi-path device?
> 
> Yes, that's a problem purely in btrfs-progs, as the path devices are
> opened exclusively for the purpose of multiapth.

  Ok. All parts of the test case is with an unmounted btrfs, I am 
clarified, now.




  reply	other threads:[~2021-09-29 12:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-28 12:37 [PATCH 1/2] btrfs-progs: Ignore path device during device scan Nikolay Borisov
2021-09-28 12:37 ` [PATCH 2/2] btrfs-progs: Ignore path devices during scan - static build support Nikolay Borisov
2021-09-29 18:46   ` David Sterba
2021-09-28 23:03 ` [PATCH 1/2] btrfs-progs: Ignore path device during device scan Anand Jain
2021-09-29  6:59   ` Nikolay Borisov
2021-09-29 11:13     ` Anand Jain
2021-09-29 11:25       ` Nikolay Borisov
2021-09-29 12:44         ` Anand Jain [this message]
2021-09-29 12:51           ` Nikolay Borisov
2021-09-30  1:02             ` Anand Jain
2021-09-29 18:38     ` David Sterba
2021-09-29 18:31 ` 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=c2828ccd-80a2-a7c9-0282-bb58046375c3@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=nborisov@suse.com \
    /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.