1

create raid10 with lvm

view story
linux-howto

http://serverfault.com – I came across an error when I create RAID10 with LVM2. I have four PVs and when I create LV using this command: sudo lvcreate --mirrors 1 --stripes 2 -l7630 -n lv0 vg0 --corelog display the VG, it should be empty,but it has half.. VG Name vg0 System ID Format lvm2 Metadata Areas 4 Metadata Sequence No 3 VG Access read/write VG Status resizable MAX LV 0 Cur LV 1 Open LV 0 Max PV 0 Cur PV 4 Act PV 4 VG Size (HowTos)

taskli's picture
Submitted by taskli on 10/08/2012

Stories similar to create raid10 with lvm

Using ubuntu 12.04,

$sudo vgdisplay ------------Volume group------------------ VG Name vol Sysytem ID Format lvm2 Metadata Areas 1 Metadata Sequence NO 1 VG Access read/write VG Status resizable MAX LV 0 Cur LV 0 Open LV 0 Max PV 0 Cur PV

Hi everyone, I use Fedora 17.

I used gparted to created a dev/sdb2 partition. I then used vgextend to extend the volume group.

Basing this question on information I got in Why does df shows only half the size of a RAID10 array?, how should I create a RAID10 array using EBS volumes on Amazon, in a way that will not be redundant too much ?

As the linked question shows, I was using a guide from the 10gen company (that created mongodb) for how to create a raid10 array using EBS.

I encounter an issue with the size of the cre

Basing this question on information I got in Why does df shows only half the size of a RAID10 array?, how should I create a RAID10 array using EBS volumes on Amazon, in a way that will not be redundant too much ?

As the linked question shows, I was using a guide from the 10gen company (that created mongodb) for how to create a raid10 array using EBS.

I encounter an issue with the size of the cre

I recently upgraded to Linux Mint from Ubuntu. I have overwritten /dev/sda2 which had Ubuntu. I had earlier created two logical volumes opt and virtualization from /dev/sda1. I forgot to take the lvm partition metadata backup. But looks like when I installed lvm2, it managed to recover this metadata.

I previously had a raid5 with mdadm using four 2TB drives.

I've created a RAID10 array using 4 75G drives, to create a storage of 150G. After everything finished (including the initial syncing), everything looked good except the output of df -h which showed only 73G storage on the designated mount point.

Details:

The machine is an m1.large Ubuntu 11.10 instance on Amazon EC2. The 4 drives are EBS drives, each is 75G in size. The RAID10 array was crea

Array info:

/dev/md0 -> /dev/sda1 and /dev/sdb1

/dev/md2 -> /dev/sda2 and /dev/sdb2

Partition info:

/boot -> /dev/md0

/ -> /dev/md1

I have two drives that are setup as RAID1 using software RAID on Redhat. I added two additional drives (same size) and I would like to conver the RAID1 to a RAID10. The problem I'm having is adding the last drive to the array.

I'm creating RAID10 array from 6 drives. When created in near layout, e.g.

mdadm --create /dev/md2 --chunk=64 --level=10 --raid-devices=6 --layout=n2 /dev/sda1 ...

Checking stripe size as reported by the system:

cat /sys/devices/virtual/block/md2/queue/optimal_io_size

Result is 196608, as expected, e.g.