All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J. Mauelshagen" <Mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] EMC Storage + LVM + XFS
Date: Mon, 28 May 2001 11:02:26 +0000	[thread overview]
Message-ID: <20010528110226.F26710@sistina.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0105251815170.7060-100000@UberGeek.coremetrics.com>; from austin@coremetrics.com on Fri, May 25, 2001 at 06:16:06PM -0500

On Fri, May 25, 2001 at 06:16:06PM -0500, Austin Gonyou wrote:
> That is my initial assumption, but I only want to make sure that vgscan
> _will_ in fact work they way it seems it should and that the private
> region of all volumes or groups will be able to be read and recovered.

Yes, it will (unless there's JAB ;-)

One of the major purposes of vgscan is to take care of changed io access
pathes to devices.

In case you add devices online using the scsi proc interface, you can use
them at their current access path and even though that likely will change after
a reboot (or reload of the driver) vgscan can catch up with the new
io configuration at startup before VG activation.

Regards,
Heinz    -- The LVM Guy --


> 
> -- 
> Austin Gonyou
> Systems Architect, CCNA
> Coremetrics, Inc.
> Phone: 512-796-9023
> email: austin@coremetrics.com
> 
> On Fri, 25 May 2001, Ragnar Kj�rstad wrote:
> 
> > On Fri, May 25, 2001 at 05:09:08PM +0200, Stephan Austermuehle wrote:
> > > On Fri, May 25, 2001 at 09:47:34AM -0500, Austin Gonyou wrote:
> > > > I don't think I'm clear on your statement. As far as I know, which is a
> > > > lot about EMC, you can definitely plug disks online. Having Linux see
> > > > them? Not necessarily so, but I believe the polling interval for the Fibre
> > > > driver will take care of that.
> > >
> > > Oh, of course the Symmetrix allows hot plugging of disks and online
> > > mapping of hypers to one or more channels via a Bin upgrade or the
> > > SDR. But at the moment I do not know any way to make Linux recognise
> > > the additional disks without reloading (rebooting) the driver. But
> > > even if there's a way to online detect new disks -- if a vgscan is
> > > necessary to tell the Linux LVM about where its VGs have gone it isn't
> > > a very smart solution because it often requires application down time.
> >
> > I believe if you write things to /proc/scsi/scsi to make linux detect
> > new devices, they will be added _after_ the existing ones. The order
> > will not be messed up until next reboot, and then vgscan will take care
> > of it. Someone please correct me if I'm wrong :)
> >
> >
> >
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2001-05-28 11:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-25  2:46 [linux-lvm] EMC Storage + LVM + XFS Austin Gonyou
2001-05-25  2:57 ` S. Michael Denton
2001-05-25  6:58   ` Stephan Austermuehle
2001-05-25 14:47     ` Austin Gonyou
2001-05-25 15:09       ` Stephan Austermuehle
2001-05-25 17:55         ` Ragnar Kjørstad
2001-05-25 23:16           ` Austin Gonyou
2001-05-28 11:02             ` Heinz J. Mauelshagen [this message]
2001-05-25 23:14         ` Austin Gonyou
  -- strict thread matches above, loose matches on Subject: below --
2001-05-25 13:30 Christian, Chip
2001-05-25 14:46 ` Austin Gonyou
2001-05-25 15:12 Christian, Chip

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=20010528110226.F26710@sistina.com \
    --to=mauelshagen@sistina.com \
    --cc=linux-lvm@sistina.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.