Table of Contents
Advertisement
Check the Limit on File Size
Performance and Availability Requirements
ARX Site Planning Guide
Table 1.3 Size of protocol in bytes.
Protocol
NFSv2
NFSv3
NFSv2 + NFSv3
CIFS
NFSv3 + CIFS or NFSv2 + CIFS
NFSv2 + NFSv3 + CIFS
For example, consider a volume with 5 million files and 1 million
directories. The estimated disk capacity needed for the volume would be
3.5 gigabytes:
• Files: (5 million) x (300 bytes per file) = 1,500,000,000 bytes or
1.5 gigabytes
• Directories: (1 million) x (2 Kbytes per directory) = 2 billion bytes or
2 gigabytes
For a volume in a single-protocol namespace this estimate would probably
be high. In a three-protocol namespace, the estimate would probably be low.
The metadata for each managed volume is stored in a single database file.
As shown, a volume with millions of files can require multiple gigabytes of
metadata. However, a file system has a limit on the size of each file. Thus,
you must verify that the file system for the metadata share can support an
individual file that is large enough to hold all metadata in its largest volume.
F5 recommends that all metadata-share candidates have good performance
and high availability. Namespace performance suffers if its metadata is
housed on a physical device that is overwhelmed, and a namespace cannot
function at all if its metadata is unavailable. Ideally, all metadata shares are
housed in a high-performance storage cluster.
Planning for a Namespace
Bytes
395
395
485
330
395
815
1 - 29
Advertisement
Table of Contents
