In <4a5d2a14.9000...@cox.net>, Ron Johnson wrote:
>On 2009-07-13 14:24, Boyd Stephen Smith Jr. wrote:
>> In <4a5b841e.7010...@cox.net>, Ron Johnson wrote:
In your case, you'll have to add at least 3 of the new PVs to the VG
before pvmove will let you begin. Are you going to move swap ont
On 2009-07-13 14:24, Boyd Stephen Smith Jr. wrote:
In <4a5b841e.7010...@cox.net>, Ron Johnson wrote:
In your case, you'll have to add at least 3 of the new PVs to the VG
before pvmove will let you begin. Are you going to move swap onto LVM?
If not, make sure your partition table for the new dr
In <537f90650907131240t37ff3fa9k2e72f498eec26...@mail.gmail.com>, Mike
Castle wrote:
>On Mon, Jul 13, 2009 at 12:24 PM, Boyd Stephen Smith
>
>Jr. wrote:
>> pvcreate /dev/sdc1
>> pvcreate /dev/sdc2
>> pvcreate /dev/sdc3
>> pvcreate /dev/sdc4
>> vgextend $vg /dev/sdc1
>> vgextend $vg /dev/sdc2
>> vg
On Mon, Jul 13, 2009 at 12:24 PM, Boyd Stephen Smith
Jr. wrote:
> pvcreate /dev/sdc1
> pvcreate /dev/sdc2
> pvcreate /dev/sdc3
> pvcreate /dev/sdc4
> vgextend $vg /dev/sdc1
> vgextend $vg /dev/sdc2
> vgextend $vg /dev/sdc3
> vgextend $vg /dev/sdc4
> pvmove /dev/sda2
> pvmove /dev/sdb
> vgreduce $vg
In <4a5b841e.7010...@cox.net>, Ron Johnson wrote:
>> In your case, you'll have to add at least 3 of the new PVs to the VG
>> before pvmove will let you begin. Are you going to move swap onto LVM?
>> If not, make sure your partition table for the new drive still has space
>> for swap.
>
>So pvmove
In <4a5b8105.2020...@cox.net>, Ron Johnson wrote:
>On 2009-07-13 12:55, Mike Castle wrote:
>> On Mon, Jul 13, 2009 at 10:41 AM, Ron Johnson
wrote:
>>> What if I want 4 "small" partitions instead of one monster 1TB
>>> partition? I've read that you need a target at least as large as the
>>> source.
On 2009-07-13 13:32, Boyd Stephen Smith Jr. wrote:
In <4a5b26b9.50...@cox.net>, Ron Johnson wrote:
I have a 640GB drive that's starting to throw errors, so I'm going
to replace it with a 1TB drive.
The 640GB (596GiB) drive is partitioned into:
sdb1 - 2GiB swap
sdb2 - 594GiB lvm2 member
When I
On 2009-07-13 12:55, Mike Castle wrote:
On Mon, Jul 13, 2009 at 10:41 AM, Ron Johnson wrote:
What if I want 4 "small" partitions instead of one monster 1TB partition?
I've read that you need a target at least as large as the source.
(I've got this aching feeling that 1TB partitions are just no
In <4a5b26b9.50...@cox.net>, Ron Johnson wrote:
>I have a 640GB drive that's starting to throw errors, so I'm going
>to replace it with a 1TB drive.
>
>The 640GB (596GiB) drive is partitioned into:
>sdb1 - 2GiB swap
>sdb2 - 594GiB lvm2 member
>
>When I get the new device, I want to create 4x 250GB
On Mon, Jul 13, 2009 at 10:41 AM, Ron Johnson wrote:
>>
>
> What if I want 4 "small" partitions instead of one monster 1TB partition?
> I've read that you need a target at least as large as the source.
>
> (I've got this aching feeling that 1TB partitions are just not a good idea,
> and that granu
On 2009-07-13 11:54, Mike Castle wrote:
Don't try to do two things at once. If something goes wrong, you
won't know which is the cause.
Just put in the new drive and partition it into swap + lvm
swapoff /dev/sda1
vi /etc/fstab # remove swap
pvcreate
vgextend
pvmove -v /dev/sdb2
What if I w
Don't try to do two things at once. If something goes wrong, you
won't know which is the cause.
Just put in the new drive and partition it into swap + lvm
swapoff /dev/sda1
vi /etc/fstab # remove swap
pvcreate
vgextend
pvmove -v /dev/sdb2
vgreduce /dev/sdb2
shutdown and remove the bad drive
On 2009-07-13 09:42, Johannes Wiedersich wrote:
Ron Johnson wrote:
When I get the new device, I want to create 4x 250GB PVs, and then move
Why? Any reason why not just less PVs?
Granularity.
--
Scooty Puff, Sr
The Doom-Bringer
--
To UN
Ron Johnson wrote:
> When I get the new device, I want to create 4x 250GB PVs, and then move
Why? Any reason why not just less PVs?
Cheers,
Johannes
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsub
14 matches
Mail list logo
