because of your messaging i thought you didn't want to use it because of the limitations stone age as you put it, your own words.P3R wrote: ↑Wed May 20, 2020 7:36 amWhy do you guess that?
I manage ZFS systems on an almost daily basis and I have the hardware to run it, so why wouldn't I want to use it? I certainly want to at least test it.
i'm sorta agreed on this... but even for normal user, just using the auto heal feature, and not using more advance features (dedupe), is still advantageous. but like you said, if they can't cope with the limitations, then they may be better off with the standard ext4 qts firmware insteadP3R wrote: ↑Wed May 20, 2020 7:36 am
Different from the marketing message though, I want users to also be aware of the limitations and disadvantages in advance so that they can make an informed decision. I also haven't noticed the stellar performance advantage marketing tell us about. I think that a lot of users with smaller NASes would be better off sticking to QTS. At least for a while until the early adopters have taken the hit and the real hardware requirements are common knowledge. I can't imagine that anybody with 4 GB RAM will be a happy user.
i'm not sure that these limitations are clearly indicated though on this page
-QuTS hero requires a NAS with at least 4GB memory.
-Inline Data Deduplication requires a NAS with at least 8GB memory (at least 32GB memory is recommended for optimal performance).
-QuTS hero is not supported by dual-controller NAS systems.
-As QTS and QuTS hero use different file systems, the NAS system must be re-initialized before switching between QTS and QuTS hero. Users must back up their data and system settings beforehand.
it's missing mention of whether it would allow creation a single static volume from the documentation I'm pretty certain this was mentioned somewhere at some point (probly in one of the youtube in the sliders, but i can't recall which one exactly). they should add that to the list of caveats on the quts hero page.