From: Theodore Tso <tytso@mit.edu>
To: Andreas Dilger <adilger@sun.com>
Cc: Karel Zak <kzak@redhat.com>,
linux-ext4@vger.kernel.org, Eric Sandeen <sandeen@redhat.com>,
mbroz@redhat.com, agk@redhat.com
Subject: Re: [PATCH] blkid: optimize dm_device_is_leaf() usage
Date: Tue, 26 Aug 2008 16:00:28 -0400 [thread overview]
Message-ID: <20080826200028.GA29936@mit.edu> (raw)
In-Reply-To: <20080826194445.GN3392@webber.adilger.int>
On Tue, Aug 26, 2008 at 01:44:45PM -0600, Andreas Dilger wrote:
> On Aug 26, 2008 10:47 -0400, Theodore Ts'o wrote:
> > I don't think you mean multipath support in terms of where there are
> > multiple paths to the same physical device ala fiber channel, but
> > rather where are multiple devices which are built on each other,
> > right? So where /dev/sda is used to create the LVM PV's, and so on,
> > right?
>
> No, in fact DM has actual mutliple-paths-to-the-same-device support,
> via "dm-multipath".
Well, *that* we have, as long as the parent devices are real
(non-devicemapper) devices.
So if /dev/sdc and /dev/sdg are both paths to the same filesystem, and
dm-multipath has created /dev/mapper/filesystem as the multipath
device to that filesystem, any devices with /dev/mapper have priority
over non-dm devices, so /dev/mapper/filesystem will get returned
first.
- Ted
next prev parent reply other threads:[~2008-08-26 20:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-25 20:48 [PATCH] blkid: optimize dm_device_is_leaf() usage Karel Zak
2008-08-26 12:24 ` Theodore Tso
2008-08-26 13:51 ` Karel Zak
2008-08-26 14:47 ` Theodore Tso
2008-08-26 18:04 ` Theodore Tso
2008-08-26 19:44 ` Andreas Dilger
2008-08-26 20:00 ` Theodore Tso [this message]
2008-08-26 20:47 ` Karel Zak
2008-08-26 23:32 ` Theodore Tso
2008-08-27 0:19 ` Karel Zak
2008-08-27 1:21 ` Theodore Tso
2008-08-27 4:40 ` Theodore Tso
2008-08-27 8:32 ` Karel Zak
2008-08-27 7:26 ` Andreas Dilger
2008-08-27 8:10 ` Karel Zak
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=20080826200028.GA29936@mit.edu \
--to=tytso@mit.edu \
--cc=adilger@sun.com \
--cc=agk@redhat.com \
--cc=kzak@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=mbroz@redhat.com \
--cc=sandeen@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox