Search results

It appears that vgcfgbackup only exports the first VG named pve and not the second one that is actually running. Is this expected behaviour? ( WARNING: Duplicate VG name pve: rj3oK2-fJha-Dnj0-ssBF-yBX5-T5Hf-copeiM (created here) takes precedence over 71h4As-Gd2h-MwFn-tjRo-QJHn-qx06-JL4Ag3)...

Thanks, I tried first option, however LVM is determined to give me a hard time. vgimportclone -t /dev/sdb1 WARNING: Duplicate VG name pve: rj3oK2-fJha-Dnj0-ssBF-yBX5-T5Hf-copeiM (created here) takes precedence over 71h4As-Gd2h-MwFn-tjRo-QJHn-qx06-JL4Ag3 WARNING: Duplicate VG name pve...

Background info: Cluster of 7 proxmox servers - in place upgrade to 4.4 failed, did 4.4 install from CD. Restored cluster, restored VMS from backups. VMS running on shared storage - no issues there Local storage seems a bit messed up after upgrade, most of my servers have multiple drives, used...

Same issue. Last node added does not show on web interface, however it does show up in corosync.conf and pvecm status

Would something like this be possible? I have been using MooseFS as my shared storage with ProxMox for about 5 years, and it has proven to be rock solid and reliable. Getting it to work with Proxmox is trivial - add moosefs repo, install moosefs-client and add entry to /etc/fstab to mount it...

Thanks, seems I missed that rather important step somehow.

cat /etc/apt/sources.list deb http://ftp.debian.org/debian jessie main contrib # security updates deb http://security.debian.org/ jessie/updates main contrib cat /etc/apt/sources.list.d/pve-no-subscription.list deb http://download.proxmox.com/debian jessie pve-no-subscription cat...

Clean install of ProxMox 3.1 on test server Upgrade to 3.4 (deb http://download.proxmox.com/debian wheezy pve-no-subscription) Upgraded no issues. reboot apt-get update && apt-get dist-upgrade apt-get remove proxmox-ve-2.6.32 pve-manager corosync-pve openais-pve redhat-cluster-pve pve-cluster...

Sorry for the extremely late reply... My MSSQL server's drive settings are as follows: Format=raw, cache=Writethrough MFS Goal for drive has been set to 4 (I have added several chunk servers since initial install) IO performance on latest MFS (2.0.27) is exceptional All servers and chunk...

I have a similar set-up (using moosefs instead of gluster) 5 node cluster, 3 of those nodes are moosefs chunk servers. (I also have independent master and chunk servers that I added later to improve performance) If you can avoid using the node as storage server you should (you really take a...

I have been running MooseFS on my small Proxmox cluster (5 hosts) for almost a year now. My MooseFS share is set up as a directory - shared storage. Performance is great so far. Two of the Proxmox Hosts function as MooseFS chunk servers without any noticeable problems (just to see if it would...