From: Phillip Susi <phill@thesusis.net>
To: Juan P C <audioprof2002@hotmail.com>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: missing Levels.
Date: Mon, 12 Feb 2024 11:19:15 -0500 [thread overview]
Message-ID: <87o7clmz98.fsf@vps.thesusis.net> (raw)
In-Reply-To: <BN0PR20MB4088BAB7BB75BACB62A29567B2492@BN0PR20MB4088.namprd20.prod.outlook.com>
Juan P C <audioprof2002@hotmail.com> writes:
> Enmotus FuzeDrive 1.6TB its actually a QLC 2TB M.2 NVMe PCIe
> that Requires Windows Raid drivers.
>
> Has built-in different technologies, All-in-one.
>
> #1. Smart Cache RAID mode...
> Small fast SSD + Larger HDD.
> Similar to intel Optane or Apple Fusion Drive,
> But both solid, smarter,
> defrag the ssd,
> moves most access files to Cache drive,
> and files with less access to Main/Large storage.
Caching isn't RAID. If you want caching, see dm-cache or bcache.
> #2. RAID2 mode.
RAID2 isn't something that really exists in the industry. According to
wikipedia, it was once used to refer to a bit level, rather than block
level type of striping with parity. These people seem to be making up
their own system and it sounds like snakeoil.
> the drive is partitioned in 2.
> 1/4 of the 2TB QLC is used in Raid level=2 mode.
>
> The reason is to emulate an SLC with QLC.
> Increase speed & longevity by 4x
> By reducing size 1/4.
I can't tell if you are talking about one drive, or two. You can't
magically speed up a single drive nor increase its longetivity.
> Real SLC are very expensive & power hungry.
> QLC are cheap.
>
> Basically 2 Raids in 1.
> Inception.
Which two? raid10 is "2 raids in 1" ( raid0 and raid1 ).
next prev parent reply other threads:[~2024-02-12 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-11 18:58 missing Levels Juan P C
2024-02-12 16:19 ` Phillip Susi [this message]
2024-02-13 10:03 ` Mariusz Tkaczyk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o7clmz98.fsf@vps.thesusis.net \
--to=phill@thesusis.net \
--cc=audioprof2002@hotmail.com \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.