An administrator is testing FA File Services configurations and unintentionally disabled User Mapping on an...

User Mapping in FA File: On a Pure Storage FlashArray, User Mapping is the mechanism that translates identities between different protocols (like mapping a Windows SID to a Unix UID/GID) or between an external directory service (like Active Directory or LDAP) and the local file system permissions.

The Impact of Disabling Mapping: When User Mapping is disabled on an active NFS export, the FlashArray can no longer resolve the identity of the user attempting to access existing files. Because NFS (specifically NFSv3 and NFSv4.1 supported by Pure) relies on these identifiers to verify file ownership and ACLs, existing files—which are tagged with specific owner IDs—become effectively " orphaned " from the perspective of the incoming request.

Access vs. Creation: * Existing Files: Accessibility is lost because the system cannot verify that the user has the rights to read or modify the file without the mapping logic.

New Files: Interestingly, in many " No Mapping " configurations, a user may still be able to create new files (often defaulting to a ' nobody ' or ' anonymous ' UID depending on the export rules), but they will immediately lose the ability to manage or access them once created because the mapping link is broken.

Real-time Application: Unlike some legacy storage systems that require a service restart, Purity applies export policy changes dynamically . As soon as the " User Mapping " toggle is disabled, the logic is removed from the data path, impacting active sessions immediately.