From: Kevin Corry <corryk@us.ibm.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org,
evms-devel@lists.sourceforge.net
Subject: Re: EVMS Submission for 2.5
Date: Thu, 3 Oct 2002 08:04:53 -0500 [thread overview]
Message-ID: <02100308045305.05904@boiler> (raw)
In-Reply-To: <Pine.GSO.4.21.0210021848420.13480-100000@weyl.math.psu.edu>
On Wednesday 02 October 2002 18:02, Alexander Viro wrote:
> On Wed, 2 Oct 2002, Kevin Corry wrote:
> > So the question is, will there be a method to simply get a list of
> > registered disks on the system, or an API to call to run a function for
> > each disk? If so, we'll gladly switch to using that. If not, do you have
> > any suggestions for how this kind of functionality can be achieved with
> > your upcoming changes?
>
> That _really_ depends on the nature of functions you want to call that
> way.
>
> I might agree with something along the lines of
> * when evms is initialized, it's notified of all existing gendisks
> * whenever disk is added after evms initialization, we notify evms
> * whenever disk is removed, we notify evms
This sounds like it would be exactly what EVMS needs. The only thing we would
want to add to this list is: "*whenever a disk is modified, notify evms". For
example, with removable media drives (such as Zip and Jaz), when a cartidge
is changed, the capacity of the drive might change, and we would like to be
notified of that event.
> However, I doubt that it's what you really want. In particular, you
> probably want to see partitioning changes as well as gendisk ones
> (and no, "evms will handle all partitioning" is _not_ an acceptable
> answer).
EVMS won't really be interested in partitioning changes. It only cares about
whole devices, i.e. minor_shift == 0.
> Moreover, "gendisk is here" != "something is in the drive".
Will there be a common method for determining "media present"? The current
method EVMS uses to determine "media changes" is somewhat inconsistent
between IDE and SCSI.
> IOW, the real question is what are you going to do with that list of
> gendisks?
EVMS will try to read volume metadata from each device and activate volumes
if it finds any pertinent metadata.
--
Kevin Corry
corryk@us.ibm.com
http://evms.sourceforge.net/
next prev parent reply other threads:[~2002-10-03 13:32 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 21:33 EVMS Submission for 2.5 Kevin Corry
2002-10-02 22:14 ` Alexander Viro
2002-10-02 22:03 ` Kevin Corry
2002-10-02 23:02 ` Alexander Viro
2002-10-03 13:04 ` Kevin Corry [this message]
2002-10-03 14:51 ` Alexander Viro
2002-10-03 14:53 ` Kevin Corry
2002-10-03 15:37 ` Alexander Viro
2002-10-03 16:13 ` Greg KH
2002-10-03 16:21 ` Alexander Viro
2002-10-03 16:30 ` Greg KH
2002-10-03 17:00 ` David Lang
2002-10-03 17:27 ` Greg KH
2002-10-03 19:52 ` [Evms-devel] " Oliver Neukum
2002-10-03 21:37 ` Greg KH
2002-10-03 21:02 ` Oliver Neukum
2002-10-03 22:56 ` Greg KH
2002-10-03 23:03 ` Alexander Viro
2002-10-04 8:07 ` Oliver Neukum
2002-10-05 0:06 ` Greg KH
2002-10-03 16:55 ` Patrick Mochel
2002-10-03 19:24 ` Linus Torvalds
2002-10-02 22:27 ` Shawn
2002-10-02 22:19 ` Shawn
2002-10-02 22:43 ` Greg KH
2002-10-03 12:13 ` Kevin Corry
2002-10-03 16:23 ` Greg KH
2002-10-03 16:51 ` Linus Torvalds
2002-10-03 21:56 ` Kevin Corry
2002-10-03 23:07 ` Greg KH
2002-10-04 0:39 ` Kevin Corry
2002-10-04 13:06 ` Alan Cox
2002-10-04 13:07 ` [Evms-devel] " Kevin Corry
2002-10-04 17:29 ` Kai Henningsen
2002-10-03 14:32 ` Christoph Hellwig
2002-10-03 14:59 ` [Evms-devel] " Michael Clark
2002-10-03 15:08 ` Christoph Hellwig
2002-10-03 15:03 ` Shawn
2002-10-03 15:31 ` Christoph Hellwig
2002-10-03 15:41 ` [Evms-devel] " Mike Tran
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=02100308045305.05904@boiler \
--to=corryk@us.ibm.com \
--cc=evms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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