4 Feb
2002
4 Feb
'02
6:53 p.m.
Neil,
If I understand the bug description correctly, it's not the "one symlink per user" alone that causes the performance problems. It's that in combination with a large "symlink.translations" file on the filer which slows things down.
We've been using 1 symlink per user since the beginning (1997), and we've been using this setup with the filer-generated CIFS homedir shares since June, with no performance issues. Like you, we have the cifs.homedir option pointing at our /home/users/ directory, which contains all the symlinks. We don't have 1000's of users, and we only have two entries in our symlink.translations file. It seems like one should be able to get by with only one or maybe a few entries per volume on your filer.
Regards,
--
Marion Hakanson hakanson@cse.ogi.edu
CSE Computing Facilities
Neil Lehrer nlehrer@ibb.gov writes:
>
> has anyone seen this issue? i am going to be using 1 symlink per user for
> homedirs because our homedir struct is not flat - h/a/aboy, h/b/balbert with
> dirs a - z.
> the homedir option will point to the homelinks dir which contains all the
> symlinks.
>
>
> Description
> Prolonged heavy access by CIFS clients that involve or cause lookup of Unix
> absolute symbolic links can affect filer performance. Because the resolution of
> absolute symlinks depends on Unix mount point information which is not available
> to CIFS clients, a table of translations is kept on the filer
> (/etc/symlink.translations). The entries in this file are order dependent and
> are searched sequentially. If a CIFS client is doing symlink lookups
> frequently, and if the entry to resolve the symlink is near the end of the file,
> and if the file is large, there can be a great deal of CPU utilization.
> . . .