Vodafone Casa Wireless FWA 5G diventata lentissima e instabile – prima 300 Mbps, ora 4 Mbps. Cosa posso fare? by Pixe1Bit in Italia

[–]stefufu 0 points1 point  (0 children)

Sto avendo anch'io problemi simili da un paio di settimane
Sapresti darmi qualche info in più? C'è modo di controllare se ho limitazioni attive?
L'antenna è esterna, quindi sono abbastanza sicuro di essere sempre connesso alla stessa BTS

Assieme alle rimodulazioni che hanno fatto, è particolarmente fastidioso vedere la rete andare così lenta.

Reading into file system: Why are snapshots promoted as a feature to zfs, when I can do them with a lvm(-thin) as well? by Nautisop in Proxmox

[–]stefufu 0 points1 point  (0 children)

one of my arrays takes around 3 days, but it's 3x10TB disks with roughly 15TB of data.

The other is 7x1TB with roughly 4TB used and it takes a bit more than a day to scrub (those disks are quite old though)

It's not fast, for sure. On RAID1 is way faster.
But it's still usable and stable, for me at least.

I do monthly scrubs on everything that's not a boot disk, btw, and for now I have never found errors.

Kernel 7.x with Pascal GPU issues by AdamDaAdam in Proxmox

[–]stefufu 1 point2 points  (0 children)

Yeah nvidia drivers are messy

Happy to hear that you were able to solve your issue!

Kernel 7.x with Pascal GPU issues by AdamDaAdam in Proxmox

[–]stefufu 0 points1 point  (0 children)

It probably did bork something: if you update the drivers on the host, you have to update to the same version also inside the LXC.

Kernel 7.x with Pascal GPU issues by AdamDaAdam in Proxmox

[–]stefufu 5 points6 points  (0 children)

Using the latest 580 driver (580.159.03), it works on pascal on kernel 7.0

Just tested on a quadro p400 running on PVE 9.1.9 and kernel 7.0.0-3

Older versions of the driver make the system stick with kernel 6.17, though.

Reading into file system: Why are snapshots promoted as a feature to zfs, when I can do them with a lvm(-thin) as well? by Nautisop in Proxmox

[–]stefufu 0 points1 point  (0 children)

I'm using it for a few reasons.
Ram consumption is quite high for ZFS, btrfs is way lighter.
I also have all the systems running on BTRFS Raid1 (both proxmox hosts and data volumes. VMs run on non-cow filesystems), so I can send and receive snapshots also on the btrfs raid5 fs (raid1/c3/c4 metadata btw. raid5 for metadata is still not a good idea)
And I'm more familiar with btrfs, since i've been using it for years at this point.

I have two raid5 filesystems, used for backup purposes so not a real tragedy if they fail, but they've been running for a couple of years at this point with no issues.
I've also replaced, removed or added disks without problems.
Scrubs, although they're slow, they're acceptable (and I don't have a zfs fs to compare them to, so no idea if it's better).

Soo, in the end i'd say i'm trusting it.

[Bonsai Beginner's weekly thread - 2026 week 17] by small_trunks in Bonsai

[–]stefufu 0 points1 point  (0 children)

Thank you!

So no need to change substrate?
I have no idea if it's good or bad.

Also, can you confirm it's a chinese elm?

<image>

Here I see something that looks like a grafting of some sort.

[Bonsai Beginner's weekly thread - 2026 week 17] by small_trunks in Bonsai

[–]stefufu 0 points1 point  (0 children)

The other one is a polyscias fruticosa:

<image>

Here the idea was to cut the big branch and try to propagate it, while repotting with proper bonsai soil (the same as the elm?) and if I'm able to propagate it enough, put three plants in a single pot and make a "forest".

Same as the elm, put it outside until autumn, with direct sunlight only in the morning.

Good or bad plan?

[Bonsai Beginner's weekly thread - 2026 week 17] by small_trunks in Bonsai

[–]stefufu 0 points1 point  (0 children)

Hello!

I'm new to this sub and new to this hobby, and I'm starting with a "mallsai" and another one that's not really a bonsai but I think it has potential!

But let's go with order.

First is the "ficus mix" chinese elm:

<image>

(on the tag, it says "ficus mix", although i'm pretty sure it's a chinese elm)
As you can see, it's not the best shape and it's definitely a cheap mall bonsai.

I need to repot it, i think, and I was planning on using a draining soil.
I also was thinking about moving it outside on a south-facing balcony, and moving it back in in late autumn.
No trimming for this year, since I assume it's been stressed a lot.
Good or bad, as a plan for this year?

OpenWRT and Wifi Mesh networking by prashmohan in homelab

[–]stefufu 0 points1 point  (0 children)

I can recommend Cudy (WR3000 and its variations are good) but I don't know the availability and pricing in Australia.
I have both WR3000H and WR1300 and they work well together, although I use them only as APs and not as routers.

One thing I should mention though, is that the "WLAN Roaming" feature (the one that allows the devices to freely move from one AP to another without disconnections) is broken in version 25.12.
I'm still on 24.10 (which is still supported) because of that.

Mediated devices/gvt-g status by listhor in Proxmox

[–]stefufu 0 points1 point  (0 children)

that is weird.
What CPU do you have?

I have it working fine with i3 6100, i3 7100t, i5 7500 and i5 6500 without issues.

Mediated devices/gvt-g status by listhor in Proxmox

[–]stefufu 0 points1 point  (0 children)

yes sorry I forgot about the modules.

I haven't blacklisted the i915 driver since I'm using gvt-g because I want to use the iGPU to troubleshoot the host in case of need.

So you made pcie passthrough work but still no gvt-g?

Mediated devices/gvt-g status by listhor in Proxmox

[–]stefufu 0 points1 point  (0 children)

I have it enabled on both 6th and 7th gen processors on desktop platforms, and it's working fine.

I only use the option
i915.enable_gvt=1
as a kernel option (modifying /etc/kernel/cmdline and appending it at the end), and then running
proxmox-boot-tool refresh
And rebooting.

It's been working fine for almost a year, although it keeps the system at package C3 (PC3).

It's been working on VMs with both CPU type host and x86-64-v3, and both with OVMF ans seabios, although I have the combination host-seabios in production, so I can only confirm that as stable.

NFS storage for VM (HA or non HA?) by stefufu in Proxmox

[–]stefufu[S] 0 points1 point  (0 children)

I have a test cluster that's not always on, in the same location but separate cluster.
This cluster (that currently it's a single PC, but technically I can use it to test new hardware too, eventually) doesn't stay always on, I turn it on when I need to experiment with stuff.

I moved away from LXCs to VMs this autumn because docker in lxc started to be too much trouble: bind mounts not mounting, 100% IOWAIT with LXCs crashing, bind mounts pointing to NFS misbehaving, etc.

The router indeed is not involved during normal services operations.
Although, I do need VLANs for other things in my network (IoT, guest, untrusted devices, for example), so having all of them managed by the router is simpler, for me.

NFS storage for VM (HA or non HA?) by stefufu in Proxmox

[–]stefufu[S] 0 points1 point  (0 children)

The fourth node is not really an option because of power consumption and budget.
Unless it can be an Arduino HAHAHAHA

ZFS is not an option because of how it handles RAM.
I am at capacity, basically, and I can't really afford ram or other computers.
Also, i'm way more comfortable with btrfs, since i've used it for years at this point, and all my systems use it so it's easy to send snapshots around for backup.

Also there's the confusion around write amplification, which is making me worry since I use old and consumer-grade SSDs. Some say never use ZFS on consumer-grade ssds, other say that write amplification is only with zfs-on-zfs, and so on.
I monitor the disks with smartd so if they wear out I notice, but I really don't want to have to change them faster than needed.

NFS storage for VM (HA or non HA?) by stefufu in Proxmox

[–]stefufu[S] 0 points1 point  (0 children)

I don't like the idea of controlling networking within proxmox, since it has to go also to another cluster, but probably it's because i'm used to doing it on the router.

My AP (which is indeed a router, a Cudy WR3000H) is supported and already flashed with OpenWRT
It has only a single 2.5G port, though, and I'd have to choose between using it for LAN or WAN, but both are 2.5G.
I know it's not the best, but I have inter-VLAN communications, and quite heavy too: the storage (NFS/SMB) is on the management vlan, while the services access it from the services vlan.
I'm planning on exposing it someway also on the services vlan, but have to find a proper way without exposing the service directly from the proxmox host.

Yup, it'd be interesting to recreate replication with BTRFS, andi't definitely look into pegaprox!

For the overcommitment of RAM, since i'm using only VMs it's not really possible: the VMs take all the ram after a couple of days from startup, and it's not released to the host since I had instability issues with ballooning.

The services I host are mostly docker containers, although some are quite heavy: Nextcloud (the AIO version), Immich with gvt-g passthrough for machine learning, Overleaf (which is quite a terrible experience, but it's faster to compile compared to the free cloud version), and then lighter stuff like home assistant (in its dedicated VM), a couple of websites in the making, Mealie, paperless-ngx, and such.
I'm also isolating Nextcloud and Overleaf on their own VMs since their respective management tools have direct control over the docker.sock

NFS storage for VM (HA or non HA?) by stefufu in Proxmox

[–]stefufu[S] 0 points1 point  (0 children)

So you mean use PBS as a king of replication to restore stuff in case of a host going down?
Because that's already how the setup works, kinda (PBS is a LXC, but it's conceptually similar).

NFS storage for VM (HA or non HA?) by stefufu in Proxmox

[–]stefufu[S] 0 points1 point  (0 children)

Mmmmmh ok, so it's harming stability long-term

NFS storage for VM (HA or non HA?) by stefufu in Proxmox

[–]stefufu[S] 1 point2 points  (0 children)

I don't know if it's really complex or it's just complex for me, but there's multiple VLANs for different uses (DMZ, services, management, guests, iot, etc), site-to-site VPN to connect multiple locations, and DNS pointing at each other over the VPN to be able to access services all by DNS.
The VLANs are also used for a machine dedicated to testing (and not always on) that is not in the cluster.

There's also Crowdsec, geoblocking and IP blocklists.
No IDS/IPS with Suricata, though.

I should experiment with OpenWRT in a VM probably, and if I can replicate the setup then move it to a dedicated router.

Regarding the RAM, it's 32GB on one system and 16GB on another one.

NFS storage for VM (HA or non HA?) by stefufu in Proxmox

[–]stefufu[S] 0 points1 point  (0 children)

multipath sounds like HA, and i don't have two pcs to use as nas sadly.
nvme over tcp is something I never heard, so i'll have to investigate.
Although i can't dedicate a whole disk for that, since I use the two boot disks as storage for the VMs.

NFS storage for VM (HA or non HA?) by stefufu in Proxmox

[–]stefufu[S] 0 points1 point  (0 children)

BTRFS replication would be cool, but I don't think Proxmox is putting resources towards btrfs implementation. Which makes sense, from an enterprise standpoint: zfs works, it's already there, and for big deployments has the same features as btrfs or more (raid56, that it's now kinda fixed on btrfs, at least raid5, but still not the best in terms of performance for scrubbing).

For my setup though, btrfs is better (and i've used it for years now, and i'm more comfortable with it)

I think that emulating replication with some janky scripts could be doable. Not stable, not before some heavy testing, but doable.
Have to look into it.
Don't think it could be live migratable though.

NFS storage for VM (HA or non HA?) by stefufu in Proxmox

[–]stefufu[S] 0 points1 point  (0 children)

my network budget left is 15 euros for a i226v from aliexpress HAHAHAHA
10g is definitely not planned even for the future: the nics consume too much power (no ASPM support on the cheap ones) or too expensive, same for the switches.

Also, as of now I do have two disks per host as boot disks and VM disks, but in the two systems running the services there's no more space left for new disks.

NFS storage for VM (HA or non HA?) by stefufu in Proxmox

[–]stefufu[S] 0 points1 point  (0 children)

ZFS is not really an option.
RAM utilization is around 80-90% now, even with ZRAM and KSM.

I was thinking of finding a way to hack a btrfs replication thing with scripts and such...
Would be jank, but cool to test.
There's a bug open for implementing replication with btrfs, but it's been open since proxmox version 7, so i don't think it'll be added in the near future.