Talk:NetApp FAS: Difference between revisions
No edit summary |
dont blindly raise flags by ignorance please |
||
Line 18: | Line 18: | ||
==Authentication== |
==Authentication== |
||
Nothing in the article about how authentication and authorization interoperate with various directories. [[Special:Contributions/1.44.43.140|1.44.43.140]] ([[User talk:1.44.43.140|talk]]) 12:04, 12 May 2014 (UTC) |
Nothing in the article about how authentication and authorization interoperate with various directories. [[Special:Contributions/1.44.43.140|1.44.43.140]] ([[User talk:1.44.43.140|talk]]) 12:04, 12 May 2014 (UTC) |
||
== Neutrality == |
|||
The article is pretty modest, it doesn't make a big point of bringing NAS appliances to a larger audience, nor the immense benefits of introducing nvram (closing the gap sun left at prestoserve), nor does it make a large point of the, well, basically the invention of copy on write filesystems. |
|||
An advertisement could sound pretty different; anyone with reasonable industry experience should think this is really neutral. |
|||
If anything, the article lacks in information about the issues the by now rather old architecture started to show. |
|||
I'm pretty sure if I pull up articles for OSS clones like Openfiler or FreeNAS those will be much more of an advertisement. |
|||
[[Special:Contributions/2001:A60:16A8:DE01:F166:9635:CA24:A655|2001:A60:16A8:DE01:F166:9635:CA24:A655]] ([[User talk:2001:A60:16A8:DE01:F166:9635:CA24:A655|talk]]) 20:24, 27 July 2015 (UTC) |
Revision as of 20:25, 27 July 2015
Computing Unassessed | ||||||||||
|
Aggregate Limits & capacity overhead
FAS2020 has been extended to 16 TB in the most recent software release 7.3.1
The capacity overhead is "working as designed" as it provides additional checksumming for enhanced security as well as file system overhead similar to ntfs, ext3 or others. This is a common practice for most enterprise storage vendors "right sizing" hard disks to enable different hard disks from different vendors in the same raid set. —Preceding unsigned comment added by 87.139.22.228 (talk) 14:55, 27 January 2009 (UTC)
x86
"although based on x86" - true to some extent, but not 100% accurate. FAS200 series appliances use MIPS processors - these are not x86. New units (FAS6080 for example), use x64 based AMD chips...
- I've removed that. --Kubanczyk (talk) 06:53, 12 May 2008 (UTC)
NVRAM vs NVMEM
The article claims that all filers have separate dedicated NVRAM. This has not been the case for several of the machines and instead they use NVMEM where a portion of the system main RAM maintains power even though the CPU and the rest of the motherboard has lost power. Examples incude the FAS250, 270, 2040, 2220, 2240, and the entire 32xx range. — Preceding unsigned comment added by 198.95.226.40 (talk) 20:59, 19 July 2012 (UTC)
Memory / RAM table is incorrect
For example, the 6280 does not have 192GB of ram but instead has half of that. The table is mixing the values for HA pairs with single controllers. — Preceding unsigned comment added by 198.95.226.40 (talk) 21:02, 19 July 2012 (UTC)
Authentication
Nothing in the article about how authentication and authorization interoperate with various directories. 1.44.43.140 (talk) 12:04, 12 May 2014 (UTC)
Neutrality
The article is pretty modest, it doesn't make a big point of bringing NAS appliances to a larger audience, nor the immense benefits of introducing nvram (closing the gap sun left at prestoserve), nor does it make a large point of the, well, basically the invention of copy on write filesystems. An advertisement could sound pretty different; anyone with reasonable industry experience should think this is really neutral. If anything, the article lacks in information about the issues the by now rather old architecture started to show.
I'm pretty sure if I pull up articles for OSS clones like Openfiler or FreeNAS those will be much more of an advertisement. 2001:A60:16A8:DE01:F166:9635:CA24:A655 (talk) 20:24, 27 July 2015 (UTC)