From: Christopher Smith <csmith@nighthawkrad.net>
To: Robin Bowes <robin-lists@robinbowes.com>
Cc: Sebastian Kuzminsky <seb.kuzminsky@gmail.com>,
linux-raid@vger.kernel.org
Subject: Re: Best way to achieve large, expandable, cheap storage?
Date: Fri, 21 Oct 2005 14:40:31 +1000 [thread overview]
Message-ID: <4358713F.1080009@nighthawkrad.net> (raw)
In-Reply-To: <43577022.5010306@robinbowes.com>
Robin Bowes wrote:
> Christopher Smith said the following on 04/10/2005 05:09:
>
>> Yep, that's pretty much bang on. The only thing you've missed is
>> using pvmove to physically move the data off the
>> soon-to-be-decomissioned PVs(/RAID arrays).
>>
>> Be warned, for those who haven't used it before, pvmove is _very_ slow.
>
>
> I've just been re-reading this thread.
[...]
> I use pvmove something like this:
>
> # pvmove /dev/md1 /dev/md3
It would actually just be 'pvmove <old md device>', but the gist is correct.
Someone else has already responded to your questions, but just something
else to be aware of with pvmove, is that it might hang your system
(requiring a hard boot) when you try and use it, although the process
will proceed and complete without error (in the background) once you
have restarted.
It's been several months since I last used pvmove, so this bug may have
been fixed, but it was certainly present on FC4 back then. Basically
running pvmove would immediately hang the system (no response to
keyboard, etc), but after a hard reboot the pvmove process would start
up and then complete in the background.
Again, this may well have been fixed and you might not see it, but just
a word of warning so your first reaction isn't something rash ;). Since
pvmove appears to do its thing by *copying* everything from one PV to
another, rather than moving it, even if the machine crashes during the
process there's no data loss.
CS
next prev parent reply other threads:[~2005-10-21 4:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 13:20 Best way to achieve large, expandable, cheap storage? Robin Bowes
2005-09-30 13:29 ` Robin Bowes
2005-09-30 18:28 ` Brad Dameron
2005-09-30 19:20 ` Dan Stromberg
2005-09-30 18:16 ` Gregory Seidman
2005-09-30 18:34 ` Andy Smith
2005-10-02 4:36 ` Christopher Smith
2005-10-02 7:09 ` Tyler
2005-10-03 3:19 ` Christopher Smith
2005-10-03 16:33 ` Sebastian Kuzminsky
2005-10-04 4:09 ` Christopher Smith
2005-10-20 10:23 ` Robin Bowes
2005-10-20 11:19 ` Gregory Seidman
2005-10-20 11:41 ` Robin Bowes
2005-10-21 4:42 ` Christopher Smith
2005-10-21 16:48 ` Gil
2005-10-21 20:08 ` Robin Bowes
2005-10-21 4:40 ` Christopher Smith [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-27 19:12 Andrew Burgess
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=4358713F.1080009@nighthawkrad.net \
--to=csmith@nighthawkrad.net \
--cc=linux-raid@vger.kernel.org \
--cc=robin-lists@robinbowes.com \
--cc=seb.kuzminsky@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).