From: Zdenek Kabelac <zkabelac@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: John Strange <johnstra10@gmail.com>
Subject: Re: Extending DM w/ new target type
Date: Fri, 02 Aug 2013 14:07:43 +0200 [thread overview]
Message-ID: <51FBA10F.7070006@redhat.com> (raw)
In-Reply-To: <CAH1aXXYQVnYndk7S6-6TM9hiuTE2xpN+4Qt8BA_36PvrQVQSsw@mail.gmail.com>
Dne 1.8.2013 19:04, John Strange napsal(a):
> two questions:
>
> 1. I'd like to use DM with a new target type. I'm porting our virtualized
> storage solution from Windows. I've been able to register my target and get
> callbacks working, but in looking at the dm-raid code, I'm concerned with how
> tightly coupled it is with the routines in md.c (multiple devices
> implementation). Is there an expectation that a DM target use the md_xxxx
> routines?
>
> 2. I used dmsetup to create a mapping for a device that my target controls.
> Is there a way to make the underlying device (e.g. /dev/sdb) not visible to
> the system? I'm paranoid about external accesses to a LUN that I'm using.
In lvm2 it's solved in a way - that we use special flags for udev to avoid
some scanning/watchrules - however all device are always available through
/dev/mapper but user visible devices are accessible via /dev/vg/lv name
which is the only suggested and supported way to use LVs.
Obviously we often get reports where users are directly playing with
/dev/dm-XXX devices or /dev/mapper/vg-lv in their scripts and configs...
But you can't hide existing devices in system from userland visibility.
Zdenek
next prev parent reply other threads:[~2013-08-02 12:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 17:04 Extending DM w/ new target type John Strange
2013-08-01 17:54 ` Alasdair G Kergon
2013-08-02 12:07 ` Zdenek Kabelac [this message]
2013-08-09 14:50 ` John Strange
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=51FBA10F.7070006@redhat.com \
--to=zkabelac@redhat.com \
--cc=dm-devel@redhat.com \
--cc=johnstra10@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 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).