CSI Driver Fails to Create Volume When Specifying Subdirectory as Location

[loner-c]

When associating the Synology CSI driver with the NAS, it appears that the location parameter can only be configured to a volume level. Configuring location: '/volume1' works correctly, but when I configure location: '/volume1/test/', it fails to work. The error message received is: Couldn't find any host available to create Volume.

Despite setting the permissions of the /volume1/test/ shared folder on the NAS to the maximum, it still does not function properly.

Steps to Reproduce:

Install and configure the Synology CSI driver.
Create a StorageClass with location: '/volume1' - this configuration works as expected.
Modify the StorageClass to use location: '/volume1/test/'.
Attempt to create a PersistentVolumeClaim (PVC) using the modified StorageClass.
Observe that the PVC creation fails with the error Couldn't find any host available to create Volume.

Additional Information:

NFS Sharing Configuration: The /volume1/test/ directory is properly shared via NFS and has full permissions granted.
Network Connectivity: Confirmed that there are no network issues between the Kubernetes cluster nodes and the NAS.
Manual Mount Test: Manually mounting the /volume1/test/ directory from a Pod within the Kubernetes cluster works successfully.