Pillar Axiom 600 Storage System
 
Pillar Axiom 500 Storage System
 

PLA-Support>Sun Systems>DISK>Pillar Axiom>SN-DK: Ax600
 

In this Document

Goal

Fix

References

Created from <SR 3-5838470981>

Applies to:

Goal

Customer query:
++++++++++++++++++
It appears that symbolic links created via NFS on UNIX are not respected when accessed via CIFS on Windows. The reverse is also true - shortcuts created via CIFS on Windows are not respected when accessed via NFS on UNIX.
 

Fix

In a mixed NFS/CIFs deployment, the support for traversing UNIX symlinks by a Windows client, and traversal of Windows shortcuts by UNIX clients is more a limitation of the client OS, rather than the Axiom. The reason for this is the inability of each respective OSes to understand how to address each others' pointers.
1) Windows came out with the Junction technology to simulate what UNIX symlinks perform, but, there is no direct translation capability within any Windows OS of native UNIX symlinks. At best, Windows has a poor man's version of creating a symlink using the mklink utility found in Windows Vista or Windows 7. Doc 1389816.1 discusses the Axiom's ability to handle Junctions or Reparse points.
2) For UNIX flavors, Windows shortcuts appear as a .lnk file, and though certain UNIX apps can understand how to use them, this is not at the OS level. Windows shortcut files are not like UNIX links (which are created at the file-system level), because shortcuts are created at the Windows OS level -- ie, they are understood by the Windows client/program that created them, and other Windows clients may not know what to do with them as well if the shortcut doesn't have the same environment as the original Windows client owner.
 

Until discussions between UNIX and Windows occurs in how to directly handle each others pointers, this OS limitation will remain.

References

This solution has no attachment