From: Arjan van de Ven <arjanv@redhat.com>
To: Joe Thornber <thornber@fib011235813.fsnet.co.uk>
Cc: Arjan van de Ven <arjanv@redhat.com>,
lvm-devel@sistina.com, Jim McDonald <Jim@mcdee.net>,
Andreas Dilger <adilger@turbolabs.com>,
linux-lvm@sistina.com, linux-kernel@vger.kernel.org,
evms-devel@lists.sourceforge.net
Subject: Re: [ANNOUNCE] LVM reimplementation ready for beta testing
Date: Fri, 1 Feb 2002 05:12:51 -0500 [thread overview]
Message-ID: <20020201051251.B10893@devserv.devel.redhat.com> (raw)
In-Reply-To: <OFBCE93B66.F7B9C14E-ON85256B52.006B8AB3@raleigh.ibm.com> <20020131125211.A8934@fib011235813.fsnet.co.uk> <20020201045518.A10893@devserv.devel.redhat.com> <20020131130913.A8997@fib011235813.fsnet.co.uk>
In-Reply-To: <20020131130913.A8997@fib011235813.fsnet.co.uk>; from thornber@fib011235813.fsnet.co.uk on Thu, Jan 31, 2002 at 01:09:13PM +0000
On Thu, Jan 31, 2002 at 01:09:13PM +0000, Joe Thornber wrote:
>
> Now our hero decides to PV move PV2 to PV4:
>
> 1. Suspend our LV (254:3), this starts queueing all io, and flushes
> all pending io.
But "flushes all pending io" is *far* from trivial. there's no current
kernel functionality for this, so you'll have to do "weird shit" that will
break easy and often.
Also "suspending" is rather dangerous because it can deadlock the machine
(think about the VM needing to write back dirty data on this LV in order to
make memory available for your move)...
Greetings,
Arjan van de Ven
next prev parent reply other threads:[~2002-02-01 10:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-31 19:52 [linux-lvm] Re: [lvm-devel] [ANNOUNCE] LVM reimplementation ready for beta testing Steve Pratt
2002-01-31 12:52 ` Joe Thornber
2002-02-01 9:55 ` [Evms-devel] " Arjan van de Ven
2002-01-31 13:09 ` Joe Thornber
2002-02-01 10:12 ` Arjan van de Ven [this message]
2002-01-31 13:35 ` Joe Thornber
2002-02-01 11:05 ` [Evms-devel] " Stephen C. Tweedie
2002-02-01 14:44 ` Alan Cox
2002-02-01 14:58 ` [Evms-devel] " Stephen C. Tweedie
2002-02-01 21:59 ` [evms-devel] [linux-lvm] " Kevin Corry
2002-01-31 21:51 ` Joe Thornber
2002-02-01 23:30 ` Alan Cox
2002-02-02 13:39 ` Andrew Clausen
2002-02-02 19:42 ` Alan Cox
2002-01-31 21:18 ` [Evms-devel] Re: [linux-lvm] Re: [lvm-devel] " Andrew Clausen
-- strict thread matches above, loose matches on Subject: below --
2002-01-30 20:22 Joe Thornber
2002-01-31 1:01 ` christophe barbé
2002-01-31 12:45 ` Heinz J . Mauelshagen
2002-01-31 18:42 ` Jeff Garzik
2002-02-01 9:03 ` Heinz J . Mauelshagen
2002-02-04 22:16 ` Bill Davidsen
2002-02-05 10:18 ` Heinz J . Mauelshagen
2002-01-31 1:53 ` Daniel Phillips
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=20020201051251.B10893@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=Jim@mcdee.net \
--cc=adilger@turbolabs.com \
--cc=evms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-lvm@sistina.com \
--cc=lvm-devel@sistina.com \
--cc=thornber@fib011235813.fsnet.co.uk \
/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