Zunächst läßt man sich mittels vgs die verfügbaren Volumegroups anzeigen.
# vgsJetzt kann man in die bestehende VG ein logisches Volume "datalv" erstellen.
VG #PV #LV #SN Attr VSize VFree
VG_XenStorage-05311684-f218-401a-0caa-dfcce1a83d68 1 8 0 wz--n- 457.99G 229.39G
# lvcreate -v -L 200G -n datalv VG_XenStorage-05311684-f218-401a-0caa-dfcce1a83d68Die LVs sind noch zu aktivieren, so dass der Host auch Zugriff darauf hat:
Finding volume group "VG_XenStorage-05311684-f218-401a-0caa-dfcce1a83d68"
Archiving volume group "VG_XenStorage-05311684-f218-401a-0caa-dfcce1a83d68" metadata (seqno 10).
Creating logical volume datalv
Creating volume group backup "/etc/lvm/backup/VG_XenStorage-05311684-f218-401a-0caa-dfcce1a83d68" (seqno 11).
Found volume group "VG_XenStorage-05311684-f218-401a-0caa-dfcce1a83d68"
Creating VG_XenStorage--05311684--f218--401a--0caa--dfcce1a83d68-datalv
Loading VG_XenStorage--05311684--f218--401a--0caa--dfcce1a83d68-datalv table
Resuming VG_XenStorage--05311684--f218--401a--0caa--dfcce1a83d68-datalv (252:6)
Clearing start of logical volume "datalv"
Creating volume group backup "/etc/lvm/backup/VG_XenStorage-05311684-f218-401a-0caa-dfcce1a83d68" (seqno 11).
Logical volume "datalv" created
# vgchange -ayNun noch ein Dateisystem drauf und mounten und das LV steht bereit.
8 logical volume(s) in volume group "VG_XenStorage-05311684-f218-401a-0caa-dfcce1a83d68" now active
# lvs
LV VG Attr LSize Origin Snap% Move Log Copy%
LV-0da77540-0ce3-4293-9718-768d36e5e908 VG_XenStorage-05311684-f218-401a-0caa-dfcce1a83d68 -wi-ao 8.50G
LV-278f5146-bbea-4220-b216-24ef76f5a8ef VG_XenStorage-05311684-f218-401a-0caa-dfcce1a83d68 -wi-ao 4.00G
LV-5cf27ec2-e798-4304-affc-5b7a3dee7e27 VG_XenStorage-05311684-f218-401a-0caa-dfcce1a83d68 -wi-a- 4.80G
LV-6a4ef2ab-c78f-4de7-ba9d-5d048a7941a6 VG_XenStorage-05311684-f218-401a-0caa-dfcce1a83d68 -wi-ao 820.00M
LV-80b296d2-9b88-4f98-b3ef-4122d8765374 VG_XenStorage-05311684-f218-401a-0caa-dfcce1a83d68 -wi-ao 9.50G
LV-9ef4f2e6-23bd-415d-acc0-f8efef3603ef VG_XenStorage-05311684-f218-401a-0caa-dfcce1a83d68 -wi-ao 512.00M
LV-a79deac9-8dfe-4136-95a0-4d5fc6adae12 VG_XenStorage-05311684-f218-401a-0caa-dfcce1a83d68 -wi-ao 512.00M
datalv VG_XenStorage-05311684-f218-401a-0caa-dfcce1a83d68 -wi-a- 200.00G
# mkfs.ext3 /dev/VG_XenStorage-05311684-f218-401a-0caa-dfcce1a83d68/datalvdisable FS-Check
mke2fs 1.39 (29-May-2006)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
26214400 inodes, 52428800 blocks
2621440 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
1600 block groups
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Writing inode tables: 696/1600
...
tune2fs -c0 -i0 /dev/VG_XenStorage-05311684-f218-401a-0caa-dfcce1a83d68/datalvmount
# mkdir -p /data
# mount /dev/VG_XenStorage-05311684-f218-401a-0caa-dfcce1a83d68/datalv /data
df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 3.8G 1.7G 1.9G 48% /
none 377M 0 377M 0% /dev/shm
/dev/mapper/VG_XenStorage--05311684--f218--401a--0caa--dfcce1a83d68-datalv
197G 188M 187G 1% /data
0 Kommentare:
Kommentar veröffentlichen