All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Lembark <lembark@wrkhors.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LILO configuration for LVM "boot" filesystem
Date: Thu, 07 Jun 2001 10:26:57 -0500	[thread overview]
Message-ID: <3B1F9D41.F150CC71@wrkhors.com> (raw)
In-Reply-To: 20010605104843.A9845@stocks.pillory.com

>     More importantly, it needs to be a lot more stable.  I will probably
> wait on having a LV for root until Linux LVM is a robust as AIX's LVM.
> Under AIX, all of your 'system' volumes (root,usr,var) are in rootvg.
> You can add a disk to rootvg, and then issue pvmove to move all of the
> blocks on the first disk to the new one, run bosboot (LILO, roughly
> speaking) to make the second drive bootable, and then reduce the first
> disk from the VG.  Thus, if your drives are hot-swappable, you can change
> out a drive completely (even if your / is mounted on it and it has active
> swap!) without every shutting down.

HP has a nice trick, the first 3 volumes have to be contiguous
at the start of the disk.  Net result is that if the VG gets
corrupted (e.g., one disk goes down and prevents quorum) you
can boot "-lm" which turns off the LVM service and leaves the
box looking like it was partitioned with boot, / & swap on line.

If LVM is used as a module and your rc.sysinit is sane (i.e., 
heavily stripped from all of the distribution standard ones)
then you can boot single user w/o locking up on a vgscan or 
vgchange.  If everything works, fine.  If not then at least
you can get going.

-- 
 Steven Lembark                                   2930 W. Palmer St.
                                                 Chicago, IL  60647
 lembark@wrkhors.com                                   800-762-1582

  parent reply	other threads:[~2001-06-07 15:26 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-04  8:07 [linux-lvm] LILO configuration for LVM "boot" filesystem Brian J. Murrell
2001-06-04 14:21 ` Ben Lutgens
2001-06-05  2:01   ` Brian J. Murrell
2001-06-05 11:56     ` Steven Lembark
2001-06-05 15:48       ` Jack McKinney
2001-06-05 18:32         ` Andreas Dilger
2001-06-06  4:07         ` Brian J. Murrell
2001-06-07 15:30           ` Steven Lembark
2001-06-07 15:43             ` Jack McKinney
     [not found]               ` <20010607182636.H3232@jensbenecke.de>
2001-06-07 16:32                 ` Jack McKinney
     [not found]                   ` <20010607191649.R3232@jensbenecke.de>
2001-06-07 19:18                     ` Jack McKinney
2001-06-07 16:39                 ` Mario 'BitKoenig' Holbe
2001-06-07 21:20                 ` Steven Lembark
2001-06-08  2:27                 ` Russell Coker
2001-06-07 21:18               ` Steven Lembark
2001-06-07 21:36                 ` Steve Wray
2001-06-07 21:37                   ` Steven Lembark
2001-06-07 21:52                     ` Steve Wray
2001-06-07 22:15                       ` Jack McKinney
2001-06-07 22:24                         ` Steve Wray
2001-06-07 22:27                           ` Steven Lembark
2001-06-07 22:23                       ` Steven Lembark
2001-06-08  2:28                         ` Russell Coker
2001-06-08  2:26                       ` Russell Coker
2001-06-07 22:29               ` Mark van Walraven
2001-06-07 22:38                 ` Steve Wray
2001-06-07 21:08             ` Michael Tokarev
     [not found]               ` <20010608153036.G21909@jensbenecke.de>
2001-06-11  0:04                 ` Mark van Walraven
2001-06-11  0:10                   ` Steven Lembark
2001-06-11  0:20                   ` Michael Tokarev
2001-06-11 11:39                     ` Russell Coker
2001-06-07 15:26         ` Steven Lembark [this message]
2001-06-05 18:00       ` Andreas Dilger
2001-06-04 17:56 ` Andreas Dilger

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=3B1F9D41.F150CC71@wrkhors.com \
    --to=lembark@wrkhors.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.