From: Joe Thornber <thornber@btconnect.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Pvmove question
Date: Tue, 28 Aug 2001 09:51:04 +0100 [thread overview]
Message-ID: <20010828095104.E283@btconnect.com> (raw)
In-Reply-To: <OF1C4B21E3.328FDE29-ON85256AB5.004B8EA6@raleigh.ibm.com>; from corryk@us.ibm.com on Mon, Aug 27, 2001 at 08:46:33AM -0500
On Mon, Aug 27, 2001 at 08:46:33AM -0500, Kevin M Corry wrote:
> > On Fri, Aug 24, 2001 at 12:31:18AM +0200, Jean-Eric Cuendet wrote:
> > >
> > > Hi,
> > > I have a pvmove question:
> > > In the man page, it's said to be careful with pvmove if you use it
> while
> > > LVM is in use.
> > > I don't really understand what is dangerous and what is safe...
> >
> > pvmove on a mounted (or otherwise in use) LV might cause curruption of
> > your data.
>
> In what cases could pvmove cause corruption on a mounted LV? Looking
> at the man page and scanning through pvmove.c, it seems to indicate
> that only a system crash during pvmove would corrupt the data. Is
> this the only case, or are there others?
Search back through the list for a response from Andrea Arcangeli. We
need to track buffer_heads that have been trhough the make_request
function so we can really can flush the LV when suspending io for the
dureation of the move. If you're not using raw io then the only
problem is a possible deadlock when under high memory pressure.
> If there are other possibilities for corruption, wouldn't it be a
> good idea to not allow pvmove's on PV's that contain mounted LVs?
IMO yes.
- Joe
next prev parent reply other threads:[~2001-08-28 8:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-27 13:46 [linux-lvm] Pvmove question Kevin M Corry
2001-08-28 8:51 ` Joe Thornber [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-13 15:20 [linux-lvm] pvmove question Peter V. Saveliev
2001-08-23 22:31 [linux-lvm] Pvmove question Jean-Eric Cuendet
2001-08-24 7:45 ` Joe Thornber
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=20010828095104.E283@btconnect.com \
--to=thornber@btconnect.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.