From: anand jain <anand.jain@oracle.com>
To: Gabriel de Perthuis <g2p.code@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/4] a structure for the disks scan for btrfs
Date: Sat, 18 May 2013 12:35:51 +0800 [thread overview]
Message-ID: <51970527.8020604@oracle.com> (raw)
In-Reply-To: <519612B1.7050601@gmail.com>
On 17/05/2013 19:21, Gabriel de Perthuis wrote:
> On Fri, 17 May 2013 18:54:38 +0800, Anand Jain wrote:
>> The idea was to introduce /dev/mapper to find for btrfs disk,
>> However I found first we need to congregate the disk scan
>> procedure at a function so it would help to consistently tune
>> it across the btrfs-progs. As of now both fi show and
>> dev scan use the disks scan they do it on their own.
>>
>> So here it would congregate btrfs-disk scans at the function
>> scan_devs_for_btrfs, adds /dev/mapper to be used to scan
>> for btrfs, and updates its calling functions and few bug fixes.
>
> Just scan /dev/block/*. That contains all block devices.
That does not help. /dev/mapper has unified dev path,
/dev/block/ don't. when multipath is enabled for a disk,
we don't have to bother to probe its non multipath block
path. using /dev/mapper helps in this context.
Thanks
Anand
next prev parent reply other threads:[~2013-05-18 4:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 10:54 [PATCH 0/4] a structure for the disks scan for btrfs Anand Jain
2013-05-17 10:54 ` [PATCH 1/4] btrfs-progs: replace filesystem show --all-devices with -d option Anand Jain
2013-05-17 10:54 ` [PATCH 2/4] btrfs-progs: label option in btrfs filesystem show is not coded Anand Jain
2013-05-17 10:54 ` [PATCH 3/4] btrfs-progs: use /dev/mapper to find the btrfs disks Anand Jain
2013-05-17 10:54 ` [PATCH 4/4] btrfs-progs: btrfs_scan_for_fsid doesn't need all the arguments Anand Jain
2013-05-17 11:21 ` [PATCH 0/4] a structure for the disks scan for btrfs Gabriel de Perthuis
2013-05-17 11:25 ` Gabriel de Perthuis
2013-05-18 4:35 ` anand jain [this message]
2013-05-30 3:40 ` [PATCH 0/6 v2] btrfs-progs: " Anand Jain
2013-05-30 3:40 ` [PATCH 1/6 v2] btrfs-progs: btrfs_scan_for_fsid doesn't need all the arguments Anand Jain
2013-05-30 3:40 ` [PATCH 2/6 v2] btrfs-progs: label option in btrfs filesystem show is not coded Anand Jain
2013-05-30 3:40 ` [PATCH 3/6 v2] btrfs-progs: update device scan usage Anand Jain
2013-05-30 3:40 ` [PATCH 4/6 v2] btrfs-progs: congregate dev scan Anand Jain
2013-05-31 8:17 ` [PATCH 4/6 v3] " Anand Jain
2013-05-30 3:40 ` [PATCH 5/6 v2] btrfs-progs: btrfs_scan_one_dir not to skip links when /dev/mapper is provided Anand Jain
2013-05-30 3:40 ` [PATCH 6/6 v2] btrfs-progs: scan /dev/mapper in filesystem show and device scan Anand Jain
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=51970527.8020604@oracle.com \
--to=anand.jain@oracle.com \
--cc=g2p.code@gmail.com \
--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).