Method and system for implementing namespace aggregation by single redirection of folders for NFS and SMB protocols

1. A system for enabling a single redirection of folders for Network File System (NFS) and Server Message Block (SMB) protocols in a Network Attached Storage (NAS) device, the system comprising:

a NAS device comprising local folders which point to a volume of the NAS and redirection folders pointing to targets external to the NAS device; and

a user interface (UI) configured to manage the redirection folders,

wherein each said redirection folder is built through a configuration using the UI,

wherein said configuration includes defining redirection data to each said redirection folders,

wherein each said redirection folder is capable of pointing to at least one of:

SMB, and NFS remote target points, responsive to an end user request via redirection data provided thereto,

wherein each said redirection folder is implemented as a single folder structure that redirects SMB clients to remote SMB shares, while redirecting NFSv4 clients to remote NFS exports at the same time, and

wherein a modification to each said redirection folder via the SMB and the NFS protocols is blocked and is carried out only via said UI,

wherein in a case of an NFSv4 redirection folder, the following actions are taken:

replying on lookup request, denying Get Current File Handle operation (GETFH) with an NFS4ERR_MOVED error; sending by the end client a new Get Attribute (GETATTR) request operation, including flag locations where the filesystem may be found (fs_locations flag); querying by the server the folder redirection data, replying to the client with the remote server information; and establishing by the end client internally new TCP connection to the remote server host and remote server path.

2. The system according to claim 1 , wherein said redirection data to the redirection folder comprise: Remote server, Remote SMB share and/or NFS export, Redirection folder location inside local NAS volume path and Redirection folder name.

3. The system according to claim 1 , wherein each redirection folder comprises a redirection folder indicator differentiating the folder from a local folder and stored inside the Mode of each directory; and per-folder information comprising details about target location referred by each redirection folder, the per-folder information being independent for each redirection folder and is needed for SMB/NFS flows to process the actual redirection logic.

4. The system according to claim 3 , wherein the per-folder information comprises remote hostname, export name for NFS redirection folder and share name for SMB redirection folder.

5. The system according to claim 1 , wherein in a case of an SMB redirection folder, the redirection folder is seen by the end client as SMB directory absolute widelink, wherein the end client is then referred to the target location in a case the client tries to follow this widelink, and wherein modification operations for SMB widelink corresponding to redirection folder are blocked.

6. A method of enabling a single redirection of folders for Network File System (NFS) and Server Message Block (SMB) protocols in a Network Attached Storage (NAS) device, the method comprising:

maintaining a NAS device comprising local folders which point to a volume of the NAS and redirection folders pointing to targets external to the NAS device;

configuring redirection data to each said redirection folders using a user interface (UI); and

pointing, via each redirection folder, to at least one of: SMB, and NFS remote target points, responsive to an end user request via redirection data provided thereto,

wherein each said redirection folder is implemented as a single folder structure that redirects SMB clients to remote SMB shares, while redirecting NFSv4 clients to remote NFS exports at the same time, and

wherein a modification to each said redirection folder via the SMB and the NFS protocols is blocked and is carried out only via said UI,

wherein in a case of an NFSv4 redirection folder, the following actions are taken: replying on lookup request, denying Get Current File Handle operation (GETFH) with an NFS4ERR_MOVED error; sending by the end client a new Get Attribute (GETATTR) request operation, including flag locations where the filesystem may be found (fs_locations flag); querying by the server the folder redirection data, replying to the client with the remote server information; and establishing by the end client internally new TCP connection to the remote server host and remote server path.

7. The method according to claim 6 , wherein said redirection data to the redirection folder comprise: Remote server, Remote SMB share and/or NFS export, Redirection folder location inside local NAS volume path and Redirection folder name.

8. The method according to claim 6 , wherein each redirection folder comprises a redirection folder indicator differentiating the folder from a local folder and stored inside the inode of each directory; and per-folder information comprising details about target location referred by each redirection folder, the per-folder information being independent for each redirection folder and is needed for SMB/NFS flows to process the actual redirection logic.

9. The method according to claim 8 , wherein the per-folder information comprises remote hostname, export name for NFS redirection folder and share name for SMB redirection folder.

10. The method according to claim 6 , wherein in a case of an SMB redirection folder, the redirection folder is seen by the end client as SMB directory absolute widelink, wherein the end client is then referred to the target location in a case the client tries to follow this widelink, and wherein modification operations for SMB widelink corresponding to redirection folder are blocked.