Search results for query: QLC

...VE itself runs fine on an old HDD because it does not read much, however it does write a lot (logs, graphs, etc.). A SATA SSD will be more than fast enough, although i would not use one with QLC flash memory myself. Ext4 of XFS does not make a difference and depends on your personal preference.

...a ZFS" that's not right! Proxmox is a extension to Debian 12.7 and in the future to Debian 13. The SSD SAMSUNG 870 QVO 4 TB has a Chiptyp: QLC thats bad. everytime 4 Bit must be written to the flash cells. that's slow. IO don't see any dram cache on the device. There may be write timeouts...

QLC drives are really the worst for ZFS. Use it in your Windows PC but not in a server. There are plenty of threads here in this forum. Just search for QLC...

is there a situation where using ashift 12 on a 512b sector size drives leads to a performance degradation? they are perfectly divisible, so I can't imagine it's too bad that will become possible once we get more boxes. the reason we're trying to hyperconverge is to maximize what we get out of...

...you have right now. 3way will have no write benefits but read benefits compared to a 2way mirror. But the main reason for 3 way is that you can loose more than one disk, just like with RAIDZ2 over RAIDZ1. Use at least half decent SSDs that don't lie about sync, don't use QLC and have a...

Welche NVMe-SSDs kannst du empfehlen? Sind die Samsung 990 Pro dafür geeignet oder bringen sie das gleiche Problem?

...das ist, wenn du die Disks durchreichst ist es vermutlich besser das Raid in der VM zu machen. Bei Consumer SSDs ganz normal, die nutzen einfach Zellen im SLC Modus als Cache, wenn das Limit erreicht wird, wird direkt im TLC oder QLC Modus weiter geschrieben. Das musst du dann in der VM machen.

MX500 is not great but P3 Plus is QLC which is terrible for ZFS. And RAIDz1 is not great for VMs. Please search the forum a bit about PLP, QLC and RAIDz1.

...be written to the system log because it was the last drive)? Maybe it was the SATA controller to which both drives are connected? Are you using QLC drives that can cause a ZFS failure because they write too slowly (which could easily happens on both drives at the same time because of the mirror)

Als Datendisk im ZFS Pool sind die für zuhause voll OK. Aber als Special Device bekommen die viel mehr kleine Writes ab. Als Special Device nehme ich als großer Read Intensive SSD Verfechter auch Mixed Use SSDs. Da sehe ich immer deutlich mehr Writes und am Ende des Tages zählen da nicht die TB...

...zu nutzen habe ich wirklich Probleme SSD: Patriot P210 128GB 2.5" SATA SSD SSD: Crucial P3 2TB M.2 PCIe Gen3 Eine Crucial P3 NVMe PCIe 3.0 x4 QLC habe ich auch mal als ZFS Bootdrive eingesetzt, nein ist die langsam und alles läuft in Zeitlupe ab. Besser wäre hier EXT4 oder komplett eine...

What is the make and model of your 4TB SSD? Consumer QLC drives will become slower than an old HDD with sustained writes.

Please tell me the operational temperature of this micron .

I'm very happy with a Micron 7450 (PRO or MAX) M.2 because it has high fsync/sec due to the PLP. Maybe search the forum for =1&c[nodes][0]=16&o=date']PLP (or QLC, which almost always also contain advise for better/enterprise drives).

@leesteken , hi, so I tried to run it with minimum, next to none, logging from rclone and it still crashed. There is probably another logging by Proxmox or the VM which is still going very high and bringing it down, can you please point me where to look for it, and how to reduce it?

@leesteken, sorry to bother you, but have you had a chance to look at the information I provided in the previous comment? ( :

Thank you again for your time, it means a lot to me! Apologies, noted, for some reason typing it out as "ProxMox" comes naturally to me while typing, its not by intent, I will try to be more careful. I am a newbie to Proxmox, so please let me know if there are other files I can also provide...

...that to matter much if the VM and the source and destination are not on that drive. Unless Proxmox is logging a lot and that brings down the QLC drive. Unless you use VirtIO SCSI single with IO Thread on each virtual disk, the virtual network and disks share a single thread for I/O (maybe...

...NAS-HDD5400RPM]->[CAHCE: SSD-SAMSUNG-870EVO-1TB]---SMB-mouted-to-Rclone--->[TARGET: SSD-SAMSUNG-870EVO-1TB - ExFAT formatted] ProxMox itself is running on an (SSD) KINGSTON NV2 M.2-2280 PCIe 4.0 NVMe 2000GB, which I guess is QLC, but if that was the issue wouldn't the whole host freeze up?

Deleting threads is not possible (except for staff members but they only seem do that for spam). It's not clear to me what SSD drive you are using. ZFS on a QLC SSD is known to become unresponsive. ZFS with heavy swapping on the host can also lead to some kind of deadlock.