2x 3TB hard disk, LVM , Proxmox

  • Thread starter Thread starter ataomega
  • Start date Start date
A

ataomega

Guest
hello


my server has 2x 3 tb hard disks, i have configured LVM before installing proxmox

now proxmox 2 is installed.

in storages list i see proxmox is using /var/lib/vz for images / containers ...

and i have added lvm vg0 but it use it only for images and ...

how to fix it?

i have configured vg0 with about 5.5TB , how proxmox can use it for containers?

i can easily reinstall debian and configure lvm and install proxmox again,

please help me , please tell steps to get this figured

best regards
 
give all details, e.g.

Code: 
pvs

lvs

df -h
 
Code: 
fdisk -l

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.




Disk /dev/sda: 3000.6 GB, 3000592982016 bytes
256 heads, 63 sectors/track, 363376 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1      266306  2147483647+  ee  GPT


WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.




Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes
256 heads, 63 sectors/track, 363376 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1      266306  2147483647+  ee  GPT


Disk /dev/md0: 536 MB, 536858624 bytes
2 heads, 4 sectors/track, 131069 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/md0 doesn't contain a valid partition table


Disk /dev/md1: 3000.1 GB, 3000052808704 bytes
2 heads, 4 sectors/track, 732434767 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/md1 doesn't contain a valid partition table


Disk /dev/dm-0: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/dm-0 doesn't contain a valid partition table


Disk /dev/dm-1: 4294 MB, 4294967296 bytes
255 heads, 63 sectors/track, 522 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/dm-1 doesn't contain a valid partition table


Disk /dev/dm-2: 5368 MB, 5368709120 bytes
255 heads, 63 sectors/track, 652 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/dm-2 doesn't contain a valid partition table


Disk /dev/dm-3: 2979.7 GB, 2979650338816 bytes
255 heads, 63 sectors/track, 362255 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/dm-3 doesn't contain a valid partition table

Code: 
 df -hFilesystem            Size  Used Avail Use% Mounted on
/dev/mapper/vg0-root   10G  2.7G  6.8G  29% /
tmpfs                 7.8G     0  7.8G   0% /lib/init/rw
udev                  7.8G  240K  7.8G   1% /dev
tmpfs                 7.8G  9.2M  7.8G   1% /dev/shm
/dev/md0              496M   40M  431M   9% /boot
/dev/mapper/vg0-tmp   5.0G   33M  5.0G   1% /tmp
/dev/mapper/vg0-home  2.8T   33M  2.8T   1% /home

Code: 
 lvs  LV   VG   Attr   LSize  Origin Snap%  Move Log Copy%  Convert
  home vg0  -wi-ao  2.71t
  root vg0  -wi-ao 10.00g
  swap vg0  -wi-ao  4.00g
  tmp  vg0  -wi-ao  5.00g

Code: 
pvs  PV         VG   Fmt  Attr PSize PFree
  /dev/md1   vg0  lvm2 a--  2.73t    0

thanks a lot
 
first, softraid is not supported installations.

to your question:
Proxmox VE stores container on local storage. this is /var/lib/vz.

In your case, you only got a size of 10 GB here.
 
as you already have 2.0 beta, you can just add another "dir" storage where you can store your container.

just use a dir wherever you like, but I recommend to use ext3 formated. just go to "datacenter/storage" and add it.
 
thanks for your replies

"you can just add another "dir" storage where you can store your container."
so there is no need for lvm , yes?
 
no, with dir I just mean a simple directory somewhere on your filesystem.

but you do not have free space in your volume group, therefore you can never use LVM snapshot backups. you should have at least 4 GB free, but I recommend 16 GB.
 
i has 2x 3 tb hard disks

i have reinstall debian like this

1000gb for /
and 2000 gb for /home

and will partition second hard disk and mount it to /home2

then i can add /home and /home2 to storages list, yes?
 
did you get the info about the missing free space in the volume group? or didn´t you plan to use LVM snapshots?
 
i have reinstalled debian, and didnt used LVM , also no software raid anymore

i has 2x 3 tb hard disks

i have reinstall debian like this

1000gb for /
and 2000 gb for /home

and will partition second hard disk and mount it to /home2

then i can add /home and /home2 to storages list, yes?
 
yes. but again, you cannot make backup with LVM snapshots in this setup.
 
You must log in or register to reply here.
Top Bottom