All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Brian J. Murrell" <lvm@interlinx.bc.ca>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] pvmove root filesystem?
Date: Thu Nov  1 23:32:01 2001	[thread overview]
Message-ID: <20011102003346.Q21136@pc.ilinx> (raw)
In-Reply-To: <20011101221529.W16554@lynx.no>

On Thu, Nov 01, 2001 at 10:15:29PM -0700, Andreas Dilger wrote:
> 
> Brian, the "pvmove" mechanism is not yet 100% safe for mounted filesystems.

Ugh.  I was hoping to not hear something like this.  Has it gotten any
better recently?  What I mean is my LVM identifies itself as:

LVM version LVM 0.9.1_beta7(ish)  by Heinz Mauelshagen  (20 June 2001)
lvm -- Module successfully initialized

which I believe is straight out of 2.4.8-ac12 (my kernel is a
2.4.8-ac12 base from Mandrake and I don't believe they do any LVM
patching -- they use what is in the AC kernels).

Am I going to run into even more problems with this verion of LVM vs.
the latest or has the "live" pvmove stuff not changed much between the
version I am running and current.

> If there is little/no activity on the filesystem while it is being moved,
> you are probably OK.

Not a good sign for root and /var, especially when /var has my mail
spool on it.

> There may be a problem with the ext3 journal, it is
> hard to say (there was a report on the ext3 mailing list, but I never got
> enough details to sort it out.

Hrm.  I am running ext3 on my filesystems as well.

> What I would suggest (for the good of all people reading) is you do this:
> 1) Make a backup of everything (obviously).

I always^Walmost always have a good backup -- daily incremental using
Amanda actually.

> 2) Give it a try.
> 3) Tell us how it worked.  Ensure you run a full (forced) e2fsck on
>    everything, preferrably after a reboot (I think if you create the
>    file /forcedfsck or so, check your rc.sysinit or equivalent) it
>    will do this at boot time.

I just don't want this to turn into a "restore my system from tape"
type of operation, especially if the system is operating (i.e.
processing mail, etc.) while it all goes down the sh*tter.  Maybe I
will contemplate it based on your thoughts of how much worse the
operation could be based on my version of LVM installed.

> It is critical that you have a full backup, as I say people have had
> problems, and there are known "holes" in the pvmove locking.

Of course.

Thanx Andreas,
b.

-- 
Brian J. Murrell

  reply	other threads:[~2001-11-01 23:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-01 22:30 [linux-lvm] pvmove root filesystem? Brian J. Murrell
2001-11-01 23:14 ` Andreas Dilger
2001-11-01 23:32   ` Brian J. Murrell [this message]
2001-11-02  0:49     ` Andreas Dilger
2001-11-02  5:20       ` Joe Thornber
2001-11-02 10:50         ` Brent Harding
2001-11-02 10:41       ` Brent Harding
2001-11-02 11:01         ` Andreas Dilger
2001-11-02 13:47           ` Brent Harding

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=20011102003346.Q21136@pc.ilinx \
    --to=lvm@interlinx.bc.ca \
    --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.