As part of BD xlator symlink interface testing, I figured out that the parameter 'linkname' contains even the mount point for example '/media/link'. I wonder we should never get the mount directory in the server part of code. I tested creating symlink with posix xlator with top git commit 751da4675cf3add21e567aebb92de2c10457afee. Here is the steps I followed: [root@host mohan]# mount -t glusterfs host:/posix /media [root@host mohan]# ls -la /media/ total 8 drwx------. 3 root root 4096 Oct 11 11:15 . dr-xr-xr-x. 20 root root 4096 Sep 28 16:40 .. [root@host mohan]# touch /media/file [root@host mohan]# ln -s /media/file /media/link [root@host mohan]# ls -la /media/ total 9 drwx------. 3 root root 4096 Oct 11 11:18 . dr-xr-xr-x. 20 root root 4096 Sep 28 16:40 .. -rw-r--r--. 1 root root 0 Oct 11 11:18 file lrwxrwxrwx. 1 root root 11 Oct 11 11:18 link -> /media/file [root@host mohan]# umount /media [root@host mohan]# mount -t glusterfs host:/posix /media/posix [root@host mohan]# ls -la /media/posix/ total 9 drwx------. 3 root root 4096 Oct 11 11:18 . drwxr-xr-x. 4 root root 4096 Oct 11 07:55 .. -rw-r--r--. 1 root root 0 Oct 11 11:18 file lrwxrwxrwx. 1 root root 11 Oct 11 11:18 link -> /media/file Directory listing of brick from server side [root@host mohan]# ls -la ~/gl/posix/ total 24 drwx------. 3 root root 4096 Oct 11 11:18 . drwx------. 4 root root 4096 Sep 28 20:20 .. -rw-r--r--. 2 root root 0 Oct 11 11:18 file drw-------. 12 root root 4096 Oct 11 11:18 .glusterfs lrwxrwxrwx. 2 root root 11 Oct 11 11:18 link -> /media/file Ideally it should be link -> file instead of /media/file When I remounted with a different directory symlink is broken. Ideally it should not create symlink with client mount directory details or am I missing some thing here?
