Recent content by IsThisThingOn

Since we have no idea about your use case, it is hard to tell. I would seriously reconsider if you actually need shared storage. Because IMHO in most cases it is not worth the downsides. If migration does not have to be real time, you can also simply create a backup to a NFS destination and...

This is just my opinion: You should use RAW on top of ZFS. All local, no network shenanigans. You should not use (and I don't think it is even possible) use RAW over NFS, where the NFS is on top of ZFS. You should not use RAW over iSCSI, where the iSCSI is on top of ZFS. You should not use...

Yesterday I wasted way too much hours migrating some VMs from Windows 10 to Windows 11, since I ran into some obscure problems. Maybe this helps someone else, because I could not find good information on my specific problems in the forums nor on reddit. What was "special" about my migration...

I simply base that on the number of lines of code. At least openvpn is more insecure, simply because it is a bloated beast. But since we are hopefully working with 2FA, API tokens and we only allow connections from the static /56 or /48 prefix, it is pretty secure anyway.

Just a heads up, not sure if this applies to you too. Today I setup a remote PBS and forgot to open up the new IPv6 WAN rule on the remote firewall. Instead of a "could not connect to remote" or something like that error, I got a "permission denied" error. So what I am trying to say is, don't...

I could be very wrong, but this is how I understand file size / record size / compression in PBS: - Backups on the host are done in 4MB chunks. - With compression enabled by default, ZSTD might compress them a little bit. - With compression enabled by default on a PBS destination that uses...

Does PBS actually make use of atime? Or is it just inherited because of ZFS upstream? TrueNAS disables atime by default for performance reasons.

That makes it even worse by introducing another abstraction layer. No. Why should that be the case? So you want to move of the storage from PVE to a ZFS box and access it over NFS? So then the no copy on write happens on your PVE host but you still have copy on write twice, plus you added NFS...

Nutzt du kein LVM? Ansonsten funktioniert vielleicht eine offline Methode: https://pve.proxmox.com/wiki/Resize_disks#Online_for_Linux_Guests

Based on your questions asked, and not even describing a clear performance goal, I would also recommend you a partner. Or you get a system that is on the save side, meaning having at least the RAM amount you have know, CPU performance you have know and combine that with a ZFS 3 way SSD mirrors...

That is a long outdated and not very good to begin with rule. Just as the old and not very good rule "don't fill your pool over 80%". My problem with both rules is that they are way too general and ignoring the actual use case. For some use cases, the rules are way too strict, and for others...

Thanks for your great support! Awesome how good proxmox support is even for the community subscription. I thought I knew how ARC works and that your new default is way, way too small. Turns out once again that you pro guys know what you are doing and I suffered from the dunning kruger effect.

Cheers mate! Now this looks more interesting: Sep 16 02:31:18 pve smartd[839]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 76 to 77 Sep 16 02:31:18 pve smartd[839]: Device: /dev/sdc [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from...

Haha, oh my gosh sorry, you are right. I just looked at the 16th and just assumed September, this has nothing to do with this shutdown :D Logs from where? Maybe I am not educated enough, but I did not see anything worthwhile in the event viewer.

Do I understand you correctly, that you also don't think it came form the GUI,API because it isn't in the PVE task list? Regarding Windows event viewer, it gets a little bit strange and I am a little bit confused what happened here. Looking output from above, one could assume that qemu-ga.exe...