Search results

really? why is that? I havent tried this on pve9 but I dont see the network stack changing that dramatically...

One thing I can say with certainty- this is caused by something that is present on your system, which was not when the OS was initially installed. To verify, install the OS (PVE) from scratch and set up your zpool, and see if it "disappears."

your disks have been wiped. this doesnt happen on its own.

having iscsi links separated is IDEAL, and works in most instances. iscsi over LACP can, AT BEST, match the performance of seperated links, but in practice this can be quite challenging. Storage vendors rarely have any control over the end user network stack. As mentioned above, separate...

try not to filter unnecessarily; what you want to see if there are PARTITIONS on those drives. lsblk output will tell. if you have partitions, its just a matter of a race condition which could be solved. if there arent- you're doing stuff beyond what you are describing here. dont bother...

Sure. the problem isnt with the networking per se; its that you're shoving 3 vlans into two nics, 2 of which really want their own interface. this would be very simply solved if you just added another interface (or 2) for non iscsi traffic. That should probably be the first layer in your...

Understatement of the year :lol: this is really prone to MTU problems and uneven IO.

It will. I've used this kind of config in the lab before. like I said, not ideal for a production environment but can be done. edit- I'll explain the logic. nic1 has mac1. nic 2 has mac2 in the above config, either mac1 or 2 is present in V0; mac1 is present in v100, and mac2 is present in...

have less vms move. the cluster manager will not do all operations concurrently.

You can. it works. Its a bad idea, but it can be done. (as an aside, its a bad idea on vmware too; iscsi interfaces dont like to share the link.) the interfaces would look like this: iface nic0 inet manual mtu 9000 iface nic1 inet manual mtu 9000 auto bond0 iface bond 0 inet...

well, you have quite the loadout. Before we begin, make sure you have multipath-boot-tools installed. it is critical for the proper ordering of devices during boot. next, I assume the disks in question are the 600GB drives. assuming you can create a new zpool with striped mirrors: zpool...

We're looking at it from opposite perspectives. the word "prefer" tells the story; to facilitate high load, you will need to do this. The key remains that backup systems are essentially passive- all the work have to occur from the sender end; If you have no load to produce, why is "optimizing"...

lets ignore the zpool for the moment. please post the output from lsblk (do NOT grep anything) ls -la /dev/disk/by-id/

This is completely backwards. PBS doesnt want anything. load is generated by the sender, and is limited by the host storage and network connection. without establishing what your load is, you're not "wasting" anything. More to the point, the payload storage is already established; you're not...

why? having PBS and its payload storage integrated into one device seems like a perfectly reasonable solution... Agreed that option 1 is a non starter.

I stand corrected. looks like you can either stick with the current deployment with no updates or support or pay AIStor. I know that's not helpful in your usecase- but considering the non commercial nature of what you provide I'd be looking at any of the beta quality open source projects. Ceph...

If Minio was mature for you, keep using it. Openmaxio IS Minio.

caching. But if you already have a pretty good idea what the drives will be doing, what difference does this make anyway?

By whom and for what purpose? its actively developed, if that's what you mean, but Proxmox has no tooling or integrated support. I've ran RGW in the past on Proxmox and the experience has been... mixed. tooling is a problem and there are conflicts. I would counsel NOT running RGW on PVE. Minio...

You hit the nail on the head of why LXC is itself not a dependable method of containerization. As an operator, you have a choice- lightweight but far more in need of maintenance (and not appropriate for high security/multitenant application,) or heavier weight and dependable. in EITHER case, PVE...