From: Steve Wray <steve@myself.gen.nz>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] which files, which physical volumes?
Date: Fri, 24 Sep 2004 18:31:15 +1200 [thread overview]
Message-ID: <4153BF33.6030008@myself.gen.nz> (raw)
In-Reply-To: <20040924061754.GD13943@percy.comedia.it>
Luca Berra wrote:
> On Fri, Sep 24, 2004 at 02:29:37PM +1200, Steve Wray wrote:
>
>> Or maybe pvmove is *still* broken, in which case I need to find the
>> files which occupy that physical volume, move them to a different
>> logical volume altogether and then forcibly remove that physical
>> volume without regard to the files that are no longer on it... and
>> hopefuly this won't cause corruption on the filesystem on that logical
>> volume.
>
> this will certainly cause corruption.
So is there any other way to decomission that physical volume that
doesn't involve pvmove?
Actually, this just got more interesting because after the last
pvmove --abort I now get this error out of pvmove -tv;
Insufficient contiguous allocatable extents (780) for logical volume
pvmove0: 1292 required
Allocation for temporary pvmove LV failed
which is new.
I am guessing here, but if I moved some of the larger files out of that
logical volume, might pvmove be able to work around this?
next prev parent reply other threads:[~2004-09-24 6:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 2:29 [linux-lvm] which files, which physical volumes? Steve Wray
2004-09-24 6:17 ` Luca Berra
2004-09-24 6:31 ` Steve Wray [this message]
2004-09-25 16:20 ` Clint Byrum
2004-09-25 16:50 ` Alasdair G Kergon
2004-09-25 22:05 ` Steve Wray
2004-09-26 23:49 ` Michael T. Babcock
2004-09-26 20:27 ` Eric Hopper
2004-09-26 20:38 ` Steve Wray
2004-09-27 0:30 ` Alasdair G Kergon
2004-09-27 7:58 ` Steve Wray
2004-09-24 19:00 ` John Stoffel
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=4153BF33.6030008@myself.gen.nz \
--to=steve@myself.gen.nz \
--cc=linux-lvm@redhat.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