Search results

I'd like to access my PVE servers on their IPv6 addresses in a DC with native IPv6 available. Currently it's impossible as the pveproxy service is not listening on IPv6. The systems have proper dual stack setup, default (high) IPv6 preferences. Could it be fixed so the pveproxy service listens...

Yeah, my bad, it's a separate package. And yes, my concern is also is that people seem to be infatuated with load values and make (mostly false) assumptions based on them.

I can't believe my eyes. This "feature" made its way into upstream. Yes, loadavg is not a very useful metric, but still gives a vague idea of the real load and practically all end every monitoring framework probes on these values. I think it's going to get in fairly quickly as the Proxmox team...

I see, thanks.

That's a long thread, what was it specifically that helped your case?

Manual move: just create a vm on the target node/storage with identical specs. Then you can stop the source vm and dd over the block device contents through ssh.

It looks like the restore process creates a target block device with smaller size than required. What is your target storage? If the source archive is not corrupted, this might be a qmrestore bug. It's also possible to copy VM disks without using vzdump, I've done it many times. But then you...

Hm, you're right. IDK why I thought of mirroring the stripe set. A similar procedure is followed when replacing a disk in a stripe of mirrors. I guess the example you posted was OP's request anyway...

What do you mean exactly and how is it related to a stripe set created by mistake instead of a mirror?

Mirrored stripes (~RAID01) are not supported in ZFS. Your only option is re-creating the pool.

I thought OP's idea was not to use separate bridges per VLAN if possible, but I might have misunderstood him. Certainly that's the other common solution besides OVS.

They differ in speed, depending on the workload (yeah, again)... More independent spindles = more iops; more stripe sets = more sequential speed. And their various mixes, of course. You can add more than 2 disks to a mirror, if that's your thing, it can increase your random reads too, as reads...

Your alternative would be raidz2 which is similar to raid6, with good sequential read/write, but your read iops might suffer (until you hit the arc). You could be good to go, though, with that kind of workload.

Average web sites are mostly random read (but of course it depends), you would benefit greatly from a large ARC. L2ARC might or might not worth it, I tend to see low utilisation with them. If you can afford it, put more ram in the server for the ARC instead. I'd suggest going with striped mirror...

That's not really accurate. The general iowait the kernel shows you is not necessarily tied to your actual workload, most often it has nothing to do with it (I mean, it they are connected but not directly because of coalescing, used queuing principle and depth, etc.). It's a general measure...

Yes, of course. But you need to take care of setting up the proper VLAN on your interfaces in each VM/CT (you can set it on the web GUI, too, IIRC).

Striped RAID1 vdevs x3 (~RAID10) and SSD slog + L2ARC on SSD vs. HWRAID RAID6 with a relatively small 512 MB cache. Why would the former be objectively slower? For what type of workload? What is the target/acceptable IOPS? The only thing to be wary of usually is the higher IOWAIT with ZFS, when...

Yes, it's possible. Eg. your trunk is connected to eth1, you add eth1 to a bridge (eg. vmbr1) and set the bridge on your VM to vmbr1 for your VM trunk interface (eth0 or whatever). I've done this for several virtual routers.

No sh*t :) Anyway don't get me wrong, vzdump is a great tool, we use it all the time without issues, but as everything else, it has its limitations. Also you're very active here, answering quickly, I appreciate and thank you for that, don't take my dissecting of this single issue an insult...

I know all that, but... You can't really stop people from using their stuff by stating it's not well supported when they have been using it before for long. When we need it, we use it. And we want to back up those CTs as well. If it's not vzdump, then it's something else. It's just less...