Thanks for the responses. I have it working as I want it to. I have a small single visible CIFS share which contains the symlinks to the real data volumes which are not visible as CIFS shares. Even though NFS reports the links as broken, my CIFS and FTP clients follow the links.

Francois

Francois Joubert wrote:

I would like to manage the symlinks in use for the whole company at a certain directory depth on our filers (FAS3050 + OnTap 7.2.2). I would like to create the following setup so that users see a single share when they browse the filer via CIFS and FTP but give them access to data spread over more than 1 aggregate, volume and qtree.

Filer_1

Aggregate_1 Data_volume_1 Qtree_1 All_data (single share visible to company) Real_dir_1 Symlnk_Real_dir_2 Symlnk_Real_dir_3 Symlnk_Real_dir_4

Aggregate_2 Data_volume_2 Qtree_2 Real_dir_2 Data_volume_3 Qtree_3 Real_dir_3 Data_volume_4 Qtree_4 Real_dir_4

I am aware that I need to configure the widelinks option. How do I create the symlinks from my admin host (FreeBSD) which mounts all the volumes over NFS for data management purposes? I don't want to use a Windows machine to create the links. My users are Win2K and MacOSX clients and access their data using CIFS and FTP (NFS may be used later).

I have a number of samba servers with this data directory setup as a single share visible to users but data spread over a number of disks. I use the unix "ln -s" command to create the necessary symlinks on the samba servers.

Feel free to point out what may be glaringly obvious.

Thanks

Francois