Search results

Honestly, I do not understand how mirror with 8 drives (I suppose you mean something like raid10) can have less space wasted (that's 4 complete drives!) than raidz2 where just capacity equal to 2 out of 8 drives is used for parity...

IIRC, there are some IPv6-related settings in /etc/sysctl.conf, try to disable it there (something like "ipv6.disable", try to set all those to "1")...

Not again...

IIRC, in driver-pack there was deb-package which I installed with dpkg. Never on Proxmox, but a few times on Debian (and vib-package on ESXi too). I also had to install smis-provider and management tools (megacli, later storcli). I do not remember any problems. Unfortunatelly I can not test it...

You can download latest drivers/firmware from LSI/Avago/Broadcom website. I have done it a few times on pure Debian, and it worked...

Remove from your crontab. I really do not understand why crontab should take care of php garbage cleaning...

1. It is not listed as error, just pure information. 2. I do not think it is necessary to play with it. The only partition that matters is /dev/sda2 (used for ZFS), which is aligned correctly. 3. I doubt you can fix it now. You could try re-install and set up partitions/ashift manually, but it...

Is it possible to disable services (i.e. pve-ha-lrm & pve-ha-crm) from web-interface now? I remember I had to do it from command-line (systemctl). There was only stop/start/restart in web-interface, so after rebooting pve-host those services were running again...

Those SD-slots on Dell (and many other) servers are good if you are using ESXi or any other OS running basically from memory (but that's not the case of PVE). If you do not want to use hdd/ssd for PVE, better choice is USB-stick or CF-card (especially those using SLC-NANDs)...

As alternative "pass-through" comes to my mind. But I'm not sure you can pass just individual port of multiport-NIC to VM. If you had multiple NICs (each with single eth-port), you could pass one NIC to every VM... But I think that solution vith individual virtual bridge is easier. Never used...

You can create separate virtual bridge for every VM, each using one eth-port...

If you want to go ZFS-way, disable p420i completely and get HBA (i.e. HP H220/H221)...

Not sure if dns helps, as both server1.example.com and server2.example.com have to resolve to the same public IP proxmox is using. And iptables-routing is done using protocol/port/ip, not fqdn. In this case I think the easiest and most reliable solution is to use reverse proxy (nginx, varnish...

Snapshot is not backup. Moreover, PVE can not do proper backup of running VM, so filesystem corruption can be expected...

Not sure what features you have in mind, but there are definitely areas where nftables surpass iptables (simplified dual-stack config, update speed, multiple targets, native set/map, etc)...

Maybe you could switch to nftables. Seems to be stable, and Debian-devs recommend to use it...

Dell PERC H700 definitely *is* true hardware-raid controller. It is based on SAS2108 SoC and supports raid5/6 too. But unlike IBM/Intel/Fujitsu/etc controllers based on SAS2108, H700 does not use reference LSI-design. Probably because of that, standard "megaraid" (megaraid_sas, megaraid_mbox)...

True, only 1 year of support. But long before that there will be new LXC and new PVE anyway...

OK, so let's close it so that you (ev. all Proxmox-team) call it "backward compatibility" (and I'll try to remember this peculiarity), but fortunately all other software-devs call it "legacy mode". Period.

So you mean 0.6.5->0.7 is backward compatibility, and 0.7->0.6.5 is backward compatibility too? No offense, but maybe you could find some time to read those two wiki-links I posted, because you are mixing things terribly. "Legacy mode" is again something quite different (as you can read on...