Search results

I understand that you had resolved the issue... The "ifup" and "idown" comands are part of the "ifupdown2" package # dpkg -L ifupdown2 /. /etc /etc/default /etc/default/networking /etc/network /etc/network/ifupdown2 /etc/network/ifupdown2/addons.conf /etc/network/ifupdown2/ifupdown2.conf...

I had the same issue. Some of the systemd network configuration was vanished, I don't know the root cause. To solve the issue in my case: apt-get install --reinstall ifupdown2 This do the trick and configure systemd network related scripts, so the network will start right in the next reboot

It's a good point @tmikaeld , you are right: disabling ZFS compression only helps for future written files. In my case I disabled ZFS compression and restored the containers from useful dump, made in servers with LVM storage instead ZFS.

I open a issue for this in bugzilla https://bugzilla.proxmox.com/show_bug.cgi?id=1467

It seems to be an old issue, but I've got the same on LXC container "vzdump" file, using "pct restore" on ZFS storage. On certain files, the ones with non-ascii characters in their names (example: with "Ñ" character in their names), the vzdump command (or any tool used on it) makes a folder...

Hello, antoniormjr this is my first post in the forum, but I'm following for years and using Proxmox for years, it's a great product I have 3 cluster, with 2 and 4 servers (and other stand-alone servers). I made a backup script, and run on every server/ https://github.com/pedroamador/pvebackup...