Search results

By default, zfs-auto-snapshot + inherit capacity of ZFS will cascade snapshots to every entry point. By messy, I meant it will then keep snapshots for root/rpool, swap, possibly every container, etc. Thats' a lot of snapshots over time ! In, my case I wanted snapshots only of my / filesytem...

Thanks a lot mira. That means ubuntu 12.0 is still supported on PVE6.x . Woa ! I though support may have been dropped by now. Funny to imagine such an OS powered by a 5.x kernel version ^^

Of course you can. I feel the result is a bit messy, that's why I prefer to do on a as-needed basis

Hello, Can someone point me to this list please ? It is mentioned in the roadmap but I can't find it anywhere. Proxmox VE 6.3 -> Container -> "Update list of supported releases for Ubuntu, Fedora and CentOS." I'd like to know, for example, which proxmox releases support Ubuntu-12.04. Many thanks,

As far as zfs-auto-snapshot package, I found better to disable it entirely zfs set com.sun:auto-snapshot=false rpool first. This property will get inherited to all FS. Then I activated it only for the proxmox system zfs set com.sun:auto-snapshot=true rpool/ROOT/pve-1. Without this, it would make...

Hello, I don't see any relation between grub and ZFS -on-root, as far as rollback is concerned. As soon as you choose zfs as install option, you get later the ability to rollback any system change you do. Software upgrade, configuration change, file removal, etc. Before any modification, do ...

Hello, I was able to use this technique successfully on OVH dedicated servers too. I'm eager to us it on in-house proxmox systems. ZFS rules really !

If you run your containers on a zfs-based storage, the following is unofficial, but verified to work (as always, do a backup before...) vzdump 100 --mode snapshot zfs set refquota=8G rpool/data/subvol-100-disk-1 cat << EOF > 100.conf.diff --- lxc/100.conf.orig 2021-01-03 12:58:03.000000000...

Hello, Thanks for your tip spirit, It worked well for me. Before /var/log/syslog used to contain lines like this : (...) corosync[1785]: notice [TOTEM ] Initializing transport (UDP/IP Unicast). (...) corosync[1785]: [TOTEM ] Initializing transport (UDP/IP Unicast). (...) corosync[1798]...

Hello, Now that this proxmox host has been deprecated, I was able to do some more tests. Restoring another unprivilegied CT fails in the same way tar: ./var/local: Cannot mkdir: Permission denied, so the issue sounds not linked to this very CT Applying the same fix setfacl -R -m user:100000:rwX...

Success ! Just had one more issue : must restart corosync after patching /etc/pve/corosync.conf with transport/version and bindnetaddr like shown in my first post. BTW the bottom of https://pve.proxmox.com/wiki/Multicast_notes#Troubleshooting needs an update I think : Carefully read the entire...

Okay, I was successfull in joining a cluster with such a firewall config : [OPTIONS] enable: 1 [IPSET management] A.B.C.D # my home IP address for management E.F.G.H # a public host in case my home IP changes... !Y.Y.Y.0/24 # ovh local network for secondNodeY Y.Y.Y.Y # secondNodeY...

Hello, nc -l -v -p 5405 -v -u wasn't working in the first place : root@ns324801:~# nc -l -v -p 5405 -v -u retrying local 0.0.0.0:5405 : Address already in use So I had to stop corosync before and it worked : root@secondNodeY:~# systemctl stop corosync root@secondNodeY:~# nc -l -v -p 5405 -v...

No, thank YOU for your support ;) Yep, seem fine. yes, pveversion -v is exactly the same. I actually applied all available updates from pve-no-subscription channel on both servers. How do I do that ? I will try with nc -u root@firstNodeX:~# timedatectl Local time: Fri 2020-12-04...

The second nodes then loops on this continously : Dec 04 12:26:55 ns324801 corosync[6032]: notice [TOTEM ] A new membership (Y.Y.Y.Y:40772) was formed. Members Dec 04 12:26:55 ns324801 corosync[6032]: [TOTEM ] A new membership (Y.Y.Y.Y:40772) was formed. Members Dec 04 12:26:55 ns324801...

Here are the corosync log after a fresh restart, I don't see any hint (but I'm a beginner) On first node : Dec 04 08:23:42 firstNodeX systemd[1]: Starting Corosync Cluster Engine... Dec 04 08:23:42 firstNodeX corosync[4797]: [MAIN ] Corosync Cluster Engine ('2.4.4-dirty'): started and ready...

Hello, and thanks for your answer ! Actually I plan to upgrade in-place just after the setup works well. I double-checked [4] (again ;-)). I also looked at [5] during my troubleshooting. There I had the confirmation that multicast should be avoided in my setup with the 100% loss metric about...

Hello, I'm hitting more or less the same issue than Add Node 3 - Waiting for Quorum except that it is for adding the second node to the cluster. First I followed basic instructions (pvecm add fisrtNodeIPAddress) and was stuck there : pvecm add X.X.X.X Please enter superuser (root) password for...

Hello, Many thanks for your interest. It gives the same result. I used : pct restore 100 /var/lib/vz/dump/vzdump-lxc-100-2020_11_29-17_38_20.tar.lzo --unprivileged 1 -storage local-zfs Same node or different machines -> no difference. Basically I'm trying to restore on a different machine...

Thanks for the workaround, it worked for me, but I find it rather complicated. setfacl -m user:100000:rwX /where/your/want/to/restore/$CTID was actually enough for me, the trick is to do it during the restore. See my thread unable to restore an unprivileged CT as unprivileged