From: Anand Jain <Anand.Jain@oracle.com>
To: George Wang <xuw2015@gmail.com>
Cc: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 2/3] btrfs: support to find missing device by path
Date: Thu, 07 May 2015 11:17:54 +0800 [thread overview]
Message-ID: <554AD962.5040707@oracle.com> (raw)
In-Reply-To: <CAPBX1xLhRXPyEMy_Dqkmsr_T-GmOUdt5Dt8yH4CMRm0UdpFkYw@mail.gmail.com>
>>> Critically we don't need this patch. right ?
>>> Anyway user of replace cli can use devid if device read fails.
> Yes, I agree it.
>>> I think David is talking about:
>>> [PATCH] device delete by devid
>>>
>>> it was critical for device delete. since there wasn't device
>>> delete by devid. I used device delete by devid instead of
>>> device path strcmp mainly because to maintain consistency
>>> between device replace and delete.
>>> the above patch set also provides code cleanups between
>>> device replace and delete codes.
> We can delete the device by devid on behalf of "btrfs_find_device".
yes. patch-set (above) uses btrfs_find_device for device delete now.
replace was already using it.
> In my opinion, the dev path is easier and humanized to use.
yes. good to have. in the long run. But not a regression/critical.
this will conflict with my patch, can you rebase on top of
above path which has some cleanups in this area as well.
> This was OK before, but now I can not replace offline device
> by path.
> So I consider it as a regression.
You mean to say you could replace the offline device using the
device path before (not devid) and now you can't ?
Then what patch introduced the regression ? Do you see any
older version replace working with offline device using the
device path ?
Thanks, Anand
next prev parent reply other threads:[~2015-05-07 3:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 9:07 [PATCH 1/3] btrfs: introduce BTRFS_BLOCK_SIZE to replace number 4096 xuw2015
2015-04-30 9:07 ` [PATCH 2/3] btrfs: support to find missing device by path xuw2015
2015-05-05 15:38 ` David Sterba
2015-05-06 9:15 ` Anand Jain
2015-05-06 9:22 ` Anand Jain
2015-05-07 2:51 ` George Wang
2015-05-07 3:17 ` Anand Jain [this message]
2015-05-07 3:47 ` George Wang
2015-04-30 9:07 ` [PATCH 3/3] btrfs: do not allow device path updated by the stale one xuw2015
2015-05-05 15:34 ` [PATCH 1/3] btrfs: introduce BTRFS_BLOCK_SIZE to replace number 4096 David Sterba
2015-05-11 6:01 ` George Wang
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=554AD962.5040707@oracle.com \
--to=anand.jain@oracle.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=xuw2015@gmail.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.