FBAP_002 practice question 9 of 15
A customer needs to support 10 million files per folder for their AI environment. What is their limiting factor on a traditional file system?
Full set: 75 questionsDomain Implement, Migrate, and Integrate FlashArray and FlashBlade Solutions
In traditional file systems, such as ext3/ext4 or UFS, each file and directory is represented by a metadata structure called an inode. The total number of inodes is typically fixed when the file system is created. A workload with a very high file count, like 10 million files in a single folder for an AI environment, can exhaust the entire pool of available inodes. Once the inodes are depleted, no new files can be created, regardless of how much free data block space remains. This makes the finite number of inodes the primary limiting factor for supporting a massive quantity of files.
A. Folders: Folders (directories) are special files that map filenames to inode numbers. While performance can degrade in a folder with millions of files, the folder itself is not the fundamental limit; the availability of inodes for the files is.
C. Threads: Threads are units of execution managed by the operating system's scheduler. They are related to processing and concurrency, not the structural capacity of a file system to store a specific number of files.
D. Blocks: Blocks are units of storage for file data. A file system can have ample free blocks (storage space) but be unable to create new files if it has run out of inodes to track them.
1. Pure Storage Official Documentation: The FlashBlade architecture was designed to overcome the limitations of traditional systems. The "FlashBlade Architecture White Paper" states, "Traditional scale-out NAS systems are typically built from legacy filers... These systems inherit the limitations of those filers, including complex caching tiers, inode limits, and painful system management." This highlights that inode limits are a known constraint in the traditional systems FlashBlade aims to replace. (Source: Pure Storage FlashBlade Architecture White Paper, Section: "FlashBlade: A New Architecture for Modern Data," Page 3).
2. University Courseware: In the widely used operating systems textbook "Operating Systems: Three Easy Pieces," the structure of a typical UNIX file system is detailed. It explains, "When a filesystem is created... the on-disk inode table is also created. This is an array of inodes... The size of this table is fixed, and thus the total number of files in the filesystem is fixed at creation time." (Source: Arpaci-Dusseau, R. H., & Arpaci-Dusseau, A. C. (2018). Operating Systems: Three Easy Pieces. Arpaci-Dusseau Books. Chapter 40: Files and Directories, Section 40.4, Page 5).
Keep practicing
Take the free FBAP_002 practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other FBAP_002 practice questions
- Question 1The customer wants to build a software QA infrastructure using modern big data tools like…
- Question 2A customer has noticed their all-flash arrays are constantly running at or near 100% load…
- Question 4A customer has hundreds of TB of data that they need to archive for 20 years. The custome…
- Question 5A FlashBlade is designed with a properly implemented single 4x40Gb/s LAG. During implemen…
- Question 6A customer wants to use and orchestration tool to manage the FlashBlade. How should the c…
- Question 7A customer wants to leverage FlashBlade to create a DataHub. Which set of applications wi…
