Cristi Mitrana wrote:
Atunci va trebui sa adaugi partitia noua in VG-ul existent si ori
folosesti lvextend+ext2resize ori direct cu e2fsadm (care insa nu
merge decat cu LVM1).
Fiind vorba de /, va trebui sa butezi de pe un live-cd (un knoppix e
suficient).
Vezi: http://tldp.org/HOWTO/LVM-HOWTO/extendlv.html
Indicat ar trebui sa ai backup la sistem ca sa fii sigur ca nu pierzi
ceva; poti exersa intr-o masina vmware toata treaba, iei un centos
minimal de pe site-ul vmware (vezi partea de appliances, exista o
imagine de Centos 5) si-i adaugi un hdd virtual apoi incerci sa-i
extinzi /.
Daca nu poti face un full backup atunci macar un backup la tabela de
partitii de pe disc (cu sfdisk -d /dev/hda) si la configuratia de lvm
(lvmbackup sau /etc/lvm/lvm.conf parca).
Pana la urma nu am mai avut rabdare si am facut toata smecheria asta
aseara ... cam in felul urmator
incepem cu fdisk
# fdisk -l
Disk /dev/hda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 13 104391 83
Linux
/dev/hda2 14 2482 19832242+ 8e
Linux LVM
# fdisk /dev/hda
Command (m for help): p
Command (m for help): n - creezi o partitie noua
Command (m for help): t - schimbi tipul partitiei create mai sus in
8e (Linux LVM)
Command (m for help): w - salvezi partition table
reboot - pentru ca kernelul sa foloseasca noua partition table
(de cautat work around pentru a nu folosi reboot pe viitor)
??? ce se intampla daca avem hdd HOT (scsi sau altceva) , o mai
trebui rebootat sistemul ?
# fdisk -l
Disk /dev/hda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 13 104391 83 Linux
/dev/hda2 14 2482 19832242+ 8e
Linux LVM
/dev/hda3 2483 9729 58211527+ 8e
Linux LVM
acum ne apucam de lvm
# lvm
lvm> pvs - listeaza 'physical volume' (partitiile fizice)
lvm> vgs - listeaza 'volume group' (grup logic format din mai multe
partitii fizice)
lvm> lvs - listeaza 'logical volume' (partitii virtuale ale unui grup)
lvm> pvcreate /dev/hda3
Physical volume "/dev/hda3" successfully created
lvm> pvs
PV VG Fmt Attr PSize PFree
/dev/hda2 VolGroup00 lvm2 a- 18.91G 32.00M
/dev/hda3 lvm2 -- 55.51G 55.51G
lvm> vgextend VolGroup00 /dev/hda3
Volume group "VolGroup00" successfully extended
lvm> vgs
VG #PV #LV #SN Attr VSize VFree
VolGroup00 2 2 0 wz--n- 74.41G 55.53G
lvm> pvs
PV VG Fmt Attr PSize PFree
/dev/hda2 VolGroup00 lvm2 a- 18.91G 32.00M
/dev/hda3 VolGroup00 lvm2 a- 55.50G 55.50G
lvm> lvs
LV VG Attr LSize Origin Snap% Move
Log Copy%
LogVol00 VolGroup00 -wi-ao 18.50G
LogVol01 VolGroup00 -wi-ao 384.00M
lvm> lvextend -L74.03G /dev/VolGroup00/LogVol00
Rounding up size to full physical extent 74.03 GB
Extending logical volume LogVol00 to 74.03 GB
Logical volume LogVol00 successfully resized
lvm> lvs
LV VG Attr LSize Origin Snap% Move
Log Copy%
LogVol00 VolGroup00 -wi-ao 74.03G
LogVol01 VolGroup00 -wi-ao 384.00M
Am termintat cu lvm-ul dar inca nu este disponibil spatiul pe care l-am
adaugat
# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
19G 16G 2.3G 88% /
/dev/hda1 99M 16M 79M 17% /boot
none 252M 0 252M 0% /dev/shm
# ext2online /dev/VolGroup00/LogVol00
ext2online v1.1.18 - 2001/03/18 for EXT2FS 0.5b
#df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
73G 16G 55G 22% /
/dev/hda1 99M 16M 79M 17% /boot
none 252M 0 252M 0% /dev/shm
Si cam asta a fost .... am facut resize la "/" si acum totul pare sa fie OK.
Ar fi posibil sa existe inconsistente sau faze nasoale din cauza ca am
operat direct pe "/" ?
Cum se poate verifica intr-un mod usor ca parca nu as da un
#fsck.ext3 /dev/mapper/VolGroup00-LogVol00
cu partitia montata ?
P.S. am dat un reboot dupa toata operatia si totul a mers snur ... nu
pare sa fie nici o problema.
Catalin C.
_______________________________________________
RLUG mailing list
RLUG@lists.lug.ro
http://lists.lug.ro/mailman/listinfo/rlug
