For clean Markdown of any page, append .md to the page URL. For a complete documentation index, see https://docs.nvidia.com/aistore/blog/llms.txt. For full documentation content, see https://docs.nvidia.com/aistore/blog/llms-full.txt.

> This is an excerpt from an article that I posted at storagetarget.com. The full text can be found at:

* [https://storagetarget.com/2024/03/30/ais-on-nfs](https://storagetarget.com/2024/03/30/ais-on-nfs)

-------------------------------------------------------

<...>

AIStore will now aggregate not only disks (or, not just disks) but also directories. Any file directories – assuming, of course, they are not nested. Any number of regular file directories that, ostensibly, may not even have underlying block devices.

Here’s what has happened:

![Upcoming](https://files.buildwithfern.com/aistore.docs.buildwithfern.com/aistore/507f5c0435b385c3f03fb21de88821deaf323662fe4a9f47aa128410ac4dff81/pages/assets/mountpaths/mpl-transition.png)

On the left and the right: an AIS cluster sandwiched between two interfaces often referred to as frontend and backend. Cluster provides the former (which inevitably entails [S3](/aistore/s3compat) but not only), and utilizes the latter to perform fast-tiering function across vendors and solutions.

## TL;DR

Long story short, the upcoming v3.23 removes the requirement that every aistore mountpath is a separate filesystem (“FS” above) that owns a block device. In the past, this block device would have to present itself at a node’s startup and wouldn’t be permitted to be used by (or shared with) any other mountpath.

Not anymore, though. Planned for late April or May 2024, the release will introduce a separate indirection called “mountpath label.”