I am not an expert on this topic, but I think you guys are mixing a lot of stuff together.
PLP is so that in case of a system halt, the drive can safely flush data in-flight (or data that resides in the drive’s DRAM or SRAM cache buffers) to the persistent or non-volatile Flash memory and...
Well, the same could be said for mirror. There is 3 way mirror and RAIDZ2-3 if you want to survive multiple drive failures.
But I agree on that RAIDZ is not good for virtualisation for many reasons and the only advantage of RAIDZ (Storage efficiency) is sometimes even not true.
Thank you guys for your feedback! Glad that you seem to like it.
I personally think that most mirror proponents focus to much on performance. That leads beginners to believe, that because they don’t need the performance, they will get away with the increased efficiency. They would say stuff...
Another simple way or option would be like TrueNAS does it.
Their TrueNAS Mini systems come with a 16GB SSD. TrueNAS itself is installed on that small SSD. The SSD is not really used for anything else, thous should hopefully not fail. And even if fails, it is not a huge problem, because you...
Sure, but one naturally assumes similar behavior than traditional HW Raid.
But since this also seems to be true:
I think the "problem" is mitigated and I was worried for nothing :)
Thank you for your response! That sounds like a good solution.
Still, it can cause problems in edge cases and thus should probably be mentioned. If the VPN itself runs on Proxmox or if the Proxmox host offers no IPMI, it could get a little bit tricky to try to remote advise none IT people how...
Wow, this thread really caught me off guard.
So with a default install, mirror will not always prevent us from total failure if a disk dies?
I am fine with using the commands provided in the docs to replace a failed drive. But this only works with a system up and running? What if the power...
Ahh so that is different :)
I would rather use two systems that don't compete for RAM and because even 11 years later still think this post is very good:
https://www.truenas.com/community/threads/please-do-not-run-freenas-in-production-as-a-virtual-machine.12484/
Well that sounds even worse to be honest.
As I understood it:
You mostly need a NAS to store your ISOs. Maybe some VMs on top for some lightweight services.
TrueNAS Scale or unraid are way better suited for this in my opinion.
Biggest difference between the two is the "real RAID" vs "fake...
Hallo zusammen
Hatte eine Proxmox 7 Kiste am laufen mit 64GB und 32GB ARC.
Um umzusteigen auf volblocksize 16k habe ich Proxmox neu installiert.
Nun scheint zfs_arc_max auf 8GB einstellt zu sein.
Wurde das was am default geändert mit Version 8?
Im manual steht noch immer noch 50%...
I know this probably does not help you much, but for a 120TB ISO host, I would use something like TrueNAS or Unraid instead.
Proxmox is a great hypervisor but not a great NAS in my opinion.
Torrenting files to a VM, which stores stuff into a zvol and then even unrar files afterwards, can be...
I am no expert, so take everything I say with a huge grain of salt :)
I could even imagine it being a performance benefit. Maybe thanks to compression, more data fits into ARC?
Yes and no. Depends on what factor we are looking at.
- Compression gains are there.
- I don't really get the IO...
I don't think this is needed in most cases, since 16k is pretty good default. Still I agree that some refresh or more noob friendly doc would help.
Isn't lz4 compression enabled by default? MariaDB probably performs better without compression, but will use way more storage.
That is definitely...
Excellent! I was worried that I am unable to restore the VMs due to a mismatch!
Guess it is time to recreate my Proxmox host and clear out ZFS fragmentation :)
Thank you for the volblock clarifications.
One last question, now that we have 16k as a default, what happens if my old 8k host goes belly up and I need to restore backups from a NFS share?
Will it use the new 16k default?
Thanks, these are the questions I was looking for :)
For Windows VMs it is 4k, so I assume it is not QEMU but the VM setting the size? But that is just a wild guess.
I get that, but is that due to Ubuntu deciding that or Proxmox?
Or to ask differently, what is the sector size on a bare metal Ubuntu?
My guess is that it is Ubuntus decision and not Proxmox, because Windows is 4k on both, bare metal and VM.
Sorry for that off-topic question, I could not find...
Not really, because it will not change the volblocksize retroactively ;) Just kidding.
Is there a reason why Linux VMs like Ubuntu use 512 instead of 4k? Or is that also adjusted with this Update?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.