Search results

great news. Why were you reluctant to say there will be another server for free accounts? Too much demand? :)

While waiting to understand what the issue is and the patch to be merged, I implemented this workaround systemctl edit pvestatd.service Add the following in the editing section: [Service] Restart=on-failure save and exit systemctl daemon-reload The service should be automatically restarted...

To use PBS v4

Can we migrate existing free version accounts to this new server?

I will try it, thanks. I would agree with you if it wasn't for the fact that I ran proxmox 8.x for 1 year on the same hardware with no issues. How would you explain that?

Has this patch been merged? I have latest upgrades but I still don't see this in the service unit file. I'll add it manually.

I have the same issue on my MS-01 system. It has worked perfectly fine until I upgraded to proxmox 9. only after the upgrade pvestatd started to suddenly stop with this kind of error in the log: Even though I didn't think it was a hw issue, I ran hw tests on memory and cpu, and no issues were...

Bookmarked also this post. You never know what can happen in these homelabs, but that's the funny part for me. It's so boring when everything's working as expected. :) It's a good thing to learn these things that can be really useful when working on customers projects. Thanks again.

These are the gems you find on this forum (via google, because forum search is not optimal unfortunately). I was getting crazy, couldn't delete a container because of a busy disk, tried 99 things and nothing worked, then I find this post, and not only I solved the issue, but I learned a lot of...

Found it: Datacenter doc. In case anybody stumbles here for the same problem, here's what I did: In /etc/pve/datacenter.cfg I added: migration: network=172.16.0.80/32,type=insecure And the Datacenter -> Options the Migration Settings was updated right away:

do you know if it's possible to do it via CLI? my problem is that I created a thunderbolt network interface manually, it's working fine, but since I created it outside of proxmox UI it doesn't appear in the Migration Settings pull down menu. Thanks.

from what I researched at the time, the issue is specific with e1000e driver and it came up only because my PBS backups were failing with strange communication errors. If you don't have any issues with those HP mini-pcs, don't bother.

On the bridge: > cat /etc/network/interfaces auto lo iface lo inet loopback iface eno1 inet manual auto vmbr0 iface vmbr0 inet static address 10.1.10.10/23 gateway 10.1.10.1 bridge-ports eno1 bridge-stp off bridge-fd 0 post-up /sbin/ethtool -K $IFACE tso off gso off...

Just implemented this, and it works as described, thanks for confirming it's actually the same thing. Out of curiosity: if it's technically the same, so it's just a way of doing a bind mount in a different way, why does this allow snapshots and the other doesn't? I mean it's just some code in...

Works for me, but exactly like it was described by @leesteken in post #8: without the leading slash on the second path). Initially, I thought it was a mistake, but with the leading slash it doesn't work. Works perfectly without it, and finally I can enable snapshots. Here's what I added to ALL...

Ok, cleaned everything on this node...did this for all labels (hourly, daily, frequent, etc.) ❯ zfs-auto-snapshot --destroy-only --verbose --label=weekly --keep=1 -r pve-data Then removed zfs-auto-snapshot debian package. All good now: ❯ zfs list -t all -r pve-data NAME...

Looks like zfs-auto-snapshot, but I never used/installed it. I'm really confused now. :( pve-data/subvol-107-disk-0@zfs-auto-snap_daily-2024-01-22-0525 44.2M - 27.4G - pve-data/subvol-107-disk-0@zfs-auto-snap_hourly-2024-01-22-0617 48.5M - 27.4G -...

Digging into man is always helpful: ❯ zfs list pve-data/subvol-107-disk-0 -o usedbysnapshots USEDSNAP 66.6G ❯ zfs list pve-data/subvol-107-disk-0 -o usedbydataset USEDDS 27.4G So it's the snapshots...could it be PBS? I didn't do any snapshot.

I see no snapshots or related descendants that could justify that USED value. But I'm looking at the UI, I think I will have to start digging deep into the ZFS CLI. I had already tried quota, but it gave me the following error: ❯ zfs set quota=50G pve-data/subvol-107-disk-0 cannot set...

Thanks a lot for this. I am optimizing a few LXCs storage size because initially I set them too large. Using refquota worked for all of them, except for one, that was initially configured at around 90-100GB: ❯ zfs list pve-data/subvol-107-disk-0 NAME USED AVAIL REFER...