| 10 | | 2. DFS are network based (i.e. the actual storage hardware is not necessarily on the nodes) but it not necessarily parallel (i.e.there may not be multiple servers that are delivering the file system). |
| 11 | | * 作者先舉 '''NFS''' 來介紹： |
| 12 | | * __'''NFS:'''__ |
| 13 | | * Primary file system for clusters, and is pretty much” plug and play” on most *nix systems. |
| 14 | | * It was the first popular file system that allowed distributed systems to share data. |
| 15 | | * __'''NFSv3:'''__ |
| 16 | | * The most popular version of NFS. It was released around 1995 and |
| 17 | | * added several features including support for 64-bit file sizes and offsets (so it can handle files larger than 4GB), asynchronous write support, and TCP as a transport layer. |
| 18 | | * __'''NFSv4:'''__ |
| 19 | | * Around 2003, NFSv4 was released with some improvements. In particular, |
| 20 | | * it added some speed improvements, strong security (with compatibility for multiple security protocols), andNFS became a stateful protocol. |
| 21 | | * __'''NFS 的效能面:'''__ |
| 22 | | * The good news for NFS and NAS is that many codes don’t require lots of I/O for good performance. These codes will run very well using NFS as the storage protocol even for large runs (100+ nodes or several hundred cores). NFS provides adequate performance until the input and output files for these codes become extremely large, or if the code is run across a very large number of processors (in the thousands). |
| 23 | | * NFS still lacks the performance and scalability required by many large clusters, but that is about to change. |
| 24 | | * __'''pNFS (NFSv4.1):'''__ |
| 25 | | * adding '''''PFS capability to the NFS protocol'''''. The goal is to improve '''''performance and scalability''''' while making the changes within a standard (recall that NFS is the only true shared file system standard). |
| 26 | | * this standard is designed to be used with file based, block based, and object based storage devices with an eye towards freeing customers from vendor lock-in. |
| 27 | | * pNFS Architecture, [[Image(pNFS_arch.png)]] |
| 28 | | * pNFS Sever 連接 Client 和 Storage ，當 Client 要存取檔案時先至 pNFS Server 查詢 Metadata 找到檔案的位置，再連接到存放檔案的 Sotrage |
| 29 | | * 作者第二個舉的是 '''Clustered NAS''' |
| 30 | | * Clustered NAS systems were developed to make NAS systems more scalable and to give them more performance |
| 31 | | * Uses several filer heads instead of a single one. The filer heads are then connected to storage. |
| 32 | | * __'''Two Arch:'''__ |
| 33 | | 1. several file heads each have some storage assigned to them. |
| 34 | | * This first approach is used by !NetApp (!NetApp-GX) |
| 35 | | 2. the filer heads are really gateways from the clients to a parallel file system. |
| 36 | | * filer heads communicate with the client using NFS over the client network but access the parallel file system on a private storage network. |
| 37 | | * This approach allows the ClusterNAS to be scaled quite large because you can just add more gateways– which also increases aggregate performance because there are more NFS gateways. |
| 38 | | * Used by Isilon. And Panasas, IBM’s GPFS, and other parallel file systems when they are running in a NFS mode. |
| 39 | | * The problem to Clustered NAS devices is that you have limited performance to the client because you are using NFS as the communication protocol. Most of the Cluster NAS solutions use a single GigE connection so you are limited to about 90-100 MB/s at most to each client. |
| | 10 | === 2.2 DFS === |
| | 11 | * '''2.2.1''' DFS are network based(i.e. the actual storage hardware is not necessarily on the nodes) but it not necessarily parallel (i.e.there may not be multiple servers that are delivering the file system). |
| | 12 | * '''2.2.2''' 作者先舉 '''NFS''' 來介紹： |
| | 13 | * __'''NFS:'''__ |
| | 14 | * Primary file system for clusters, and is pretty much” plug and play” on most *nix systems. |
| | 15 | * It was the first popular file system that allowed distributed systems to share data. |
| | 16 | * __'''NFSv3:'''__ |
| | 17 | * The most popular version of NFS. It was released around 1995 and |
| | 18 | * added several features including support for 64-bit file sizes and offsets (so it can handle files larger than 4GB), asynchronous write support, and TCP as a transport layer. |
| | 19 | * __'''NFSv4:'''__ |
| | 20 | * Around 2003, NFSv4 was released with some improvements. In particular, |
| | 21 | * it added some speed improvements, strong security (with compatibility for multiple security protocols), and NFS became a stateful protocol. |
| | 22 | * __'''NFS 的效能面：'''__ |
| | 23 | * The good news for NFS and NAS is that many codes don’t require lots of I/O for good performance. These codes will run very well using NFS as the storage protocol even for large runs (100+ nodes or several hundred cores). NFS provides adequate performance until the input and output files for these codes become extremely large, or if the code is run across a very large number of processors (in the thousands). |
| | 24 | * NFS still lacks the performance and scalability required by many large clusters, but that is about to change. |
| | 25 | * __'''pNFS (NFSv4.1):'''__ |
| | 26 | * adding '''''PFS capability to the NFS protocol'''''. The goal is to improve '''''performance and scalability''''' while making the changes within a standard (recall that NFS is the only true shared file system standard). |
| | 27 | * this standard is designed to be used with file based, block based, and object based storage devices with an eye towards freeing customers from vendor lock-in. |
| | 28 | * pNFS Architecture, [[Image(pNFS_arch.png)]] |
| | 29 | * pNFS Sever 連接 Client 和 Storage ，當 Client 要存取檔案時先至 pNFS Server 查詢 Metadata 找到檔案的位置，再連接到存放檔案的 Sotrage |
| | 30 | * '''2.2.3''' 作者第二個舉的是 '''Clustered NAS：''' |
| | 31 | * Clustered NAS systems were developed to make NAS systems more scalable and to give them more performance |
| | 32 | * Uses several filer heads instead of a single one. The filer heads are then connected to storage. |
| | 33 | * __'''Two Arch：'''__ |
| | 34 | 1. several file heads each have some storage assigned to them. |
| | 35 | * First approach is used by !NetApp (!NetApp-GX) |
| | 36 | 2. the filer heads are really gateways from the clients to a parallel file system. |
| | 37 | * filer heads communicate with the client using NFS over the client network but access the parallel file system on a private storage network. |
| | 38 | * allows the ClusterNAS to be scaled quite large because you can just add more gateways– which also increases aggregate performance because there are more NFS gateways. |
| | 39 | * Used by Isilon. And Panasas, IBM’s GPFS, and other parallel file systems when they are running in a NFS mode. |
| | 40 | * The problem is that you have limited performance to the client because you are using NFS as the communication protocol. Most of the Cluster NAS solutions use a single GigE connection so you are limited to about 90-100 MB/s at most to each client. |
