Peter Beck:
> On 06/05/2011 04:51 PM, Jochen Schulz wrote:
>> What I would probably do is:
>>
>> - install new disk alongside the old one
>> - put one big partition on the new disk and pvcreate the partition
>> - vgextend the existing VG with the new partition
>> - vgreduce the VG, removing the ol
On 06/05/2011 04:51 PM, Jochen Schulz wrote:
What I would probably do is:
- install new disk alongside the old one
- put one big partition on the new disk and pvcreate the partition
- vgextend the existing VG with the new partition
- vgreduce the VG, removing the old disk's partitions
That shou
Gilles Mocellin:
> On dim. 05 juin 2011 16:51:26 CEST, Jochen Schulz
> wrote:
>>
>> What I would probably do is:
>>
>> - install new disk alongside the old one
>> - put one big partition on the new disk and pvcreate the partition
>> - vgextend the existing VG with the new partition
>> - vgreduc
On dim. 05 juin 2011 16:51:26 CEST, Jochen Schulz wrote:
> Peter Beck:
> >
> > Now I've got a 1TB disk which I would like to use instead of the
> > 160GB disk. My question: Can I just clone the small disk to the new
> > large disk and then resize the LV on it ? Does that work ? I would
> > say y
Peter Beck:
>
> Now I've got a 1TB disk which I would like to use instead of the
> 160GB disk. My question: Can I just clone the small disk to the new
> large disk and then resize the LV on it ? Does that work ? I would
> say yes, but I've never done that, so I am not sure... ;)
What I would prob
Hi guys,
I'm using two HP Microservers with a Heartbeat1 cluster, drbd and kvm.
On one of these servers the systemdisk is a 160GB disk with LVM
configured, on the other node it's a 1TB disk. I'd like to have both
nodes with the same disk sizes (easier to configure imo)
Now I've got a 1TB disk
6 matches
Mail list logo