(unknown)

Florian Schmid via Toasters <[email protected]> Mon, 16 Oct 2023 10:53:29 +0100
Newsgroups gmane.comp.hardware.netapp
Message-ID <[email protected]>
--===============3596397840507881097==
Content-Type: message/rfc822
Content-Disposition: inline

Received: from mx2-at.ubimet.com (mx2-at.ubimet.com [141.98.226.72])
 by dormouse.teaparty.net (8.14.7/8.14.7) with ESMTP id 39G9rM9T012708
 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO)
 for <[email protected]>; Mon, 16 Oct 2023 10:53:23 +0100
Authentication-Results: dormouse.teaparty.net;
 spf=pass [email protected]
 smtp.helo=mx2-at.ubimet.com
Received: from localhost (localhost [127.0.0.1])
 by mx2-at.ubimet.com (Postfix) with ESMTP id 0202081366
 for <[email protected]>; Mon, 16 Oct 2023 09:53:21 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ubimet.com;
 s=20200131mdel; t=1697450001;
 bh=GxSF1zvGqQbb3DPnpKYW75V+6lP0/0nEY5KrECUDwIY=;
 h=Date:From:To:Subject:From;
 b=KwyMhohFBrbRX8xTIXXn9KKuHic5ouVHhyMy254pw+vcxPzg010RVxWOJJlqmilPl
 CI+L1svQidkp9uHBFQvpzCzsU2TSHcktumA+kUNaBD+DbdwlFFn9oInSu3RRgzkBJO
 8VwOuZXYbihw5dM1DnYHkwDmWmpHBNtJKsOUas5Q1ChQOgotRvNP+I83H5Xq1klxLh
 g7NDri+ZQd8k4lvQdEHV2I0G73xVYJB3AwKhUmbSUDXBupmgA3uTp/7bcs7M39vPmX
 YgmMPBPcBrHkSAv133eoYz1itjc9JfSjdnwS3y5WHnpDV5P34x2bX0f+XYvmJXPIio
 NoTQeaJolqobg==
Received: from mx2-at.ubimet.com ([127.0.0.1])
 by localhost (mx02.dmz.dc.at.ubimet.com [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id TB0n_nkYQus0 for <[email protected]>;
 Mon, 16 Oct 2023 09:53:20 +0000 (UTC)
Received: from zimbra-mta01.ext.dc.at.ubimet.com (webmail-dc.at.ubimet.com
 [10.1.18.22])
 by mx2-at.ubimet.com (Postfix) with ESMTPS id E68EC812FD
 for <[email protected]>; Mon, 16 Oct 2023 09:53:20 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by zimbra-mta01.ext.dc.at.ubimet.com (Postfix) with ESMTP id E1A4080585
 for <[email protected]>; Mon, 16 Oct 2023 09:53:20 +0000 (UTC)
Received: from zimbra-mta01.ext.dc.at.ubimet.com ([127.0.0.1])
 by localhost (zimbra-mta01.ext.dc.at.ubimet.com [127.0.0.1]) (amavis,
 port 10032) with ESMTP id 6v3Rg39CNTeu for <[email protected]>;
 Mon, 16 Oct 2023 09:53:20 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by zimbra-mta01.ext.dc.at.ubimet.com (Postfix) with ESMTP id 318C0805E8
 for <[email protected]>; Mon, 16 Oct 2023 09:53:20 +0000 (UTC)
X-Virus-Scanned: amavis at zimbra-mta01.ext.dc.at.ubimet.com
Received: from zimbra-mta01.ext.dc.at.ubimet.com ([127.0.0.1])
 by localhost (zimbra-mta01.ext.dc.at.ubimet.com [127.0.0.1]) (amavis,
 port 10026) with ESMTP id vB3dST1lK74N for <[email protected]>;
 Mon, 16 Oct 2023 09:53:19 +0000 (UTC)
Received: from zimbra-store02.ext.dc.at.ubimet.com
 (zimbra-store02.ext.dc.at.ubimet.com [10.1.18.23])
 by zimbra-mta01.ext.dc.at.ubimet.com (Postfix) with ESMTP id E2BD280585
 for <[email protected]>; Mon, 16 Oct 2023 09:53:19 +0000 (UTC)
Date: Mon, 16 Oct 2023 09:53:19 +0000 (UTC)
From: Florian Schmid <[email protected]>
To: [email protected]
Message-ID: <[email protected]>
Subject: Question about flash pool maximum SSD size and local tiering
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.15.100.3]
X-Mailer: Zimbra 8.8.15_GA_4562 (ZimbraWebClient - GC117 (Linux)/8.8.15_GA_3)
Thread-Index: KxD2D78xIi5kja0b6I2drw+eOy5Otg==
Thread-Topic: Question about flash pool maximum SSD size and local tiering
X-Greylist: Recipient e-mail whitelisted, not delayed by milter-greylist-4.6.2
 (dormouse.teaparty.net [178.18.123.145]);
 Mon, 16 Oct 2023 10:53:24 +0100 (BST)

Hi,

I have checked NetApp HWU for a FAS 8300 and system cache limits.

Ok, so far, max flash-pool is 72 TB, which is a way more than I want to use, but I haven't seen usable SSDs greater than 3.8 TB.

Is that really true, that I can't use a 7.6 TB or 15.3 TB SSD for flash-pool?

It would be nice, if someone has here a deeper understanding than I have about this and can give me here some clarifications.

May I ask a second question?
Is flash-pool still the way to go for speeding up NL-SAS aggregates?
I had a look on fabric-pool tiering, but it seems like, that this only works to S3 storage, which we don't have.
We have plenty of NL-SAS storage and also of SSDs and it would be great to have a tiering between them or at least use them for caching.

Best regards,
Florian

--===============3596397840507881097==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Toasters mailing list
[email protected]
https://www.teaparty.net/mailman/listinfo/toasters
--===============3596397840507881097==--