The issue here is that Solaris CIFS server does not support child mount points. In other words, if you mount a file system within another file system, although you would see the child file system as a directory but CIFS server cannot simply cross the mount point when you're operating in the parent file system context which is what you're seeing here.
This issue has come up before and the reasons for not supporting it at the moment has been discussed. Due to higher priority tasks, we don't have any plans to support this in near future. Afshin [EMAIL PROTECTED] wrote: > Afshin, > > Please find attached the output of the script you requested. > >> - The user you're logged in on your Windows client > > The shares are mounted as user "remcol" > >> - Output of "ls -Vd" for pardatapool, fs2, and fs2_sub > > bash-3.2# ls -Vd pardatapool/ > drwxrwxrwx 5 root root 5 Nov 1 14:21 pardatapool/ > owner@:--------------:-------:deny > owner@:rwxp---A-W-Co-:-------:allow > group@:--------------:-------:deny > group@:rwxp----------:-------:allow > everyone@:-------A-W-Co-:-------:deny > everyone@:rwxp--a-R-c--s:-------:allow > bash-3.2# ls -Vd pardatapool/fs2/ > drwxr-xr-x 3 remcol root 4 Nov 1 14:26 pardatapool/fs2/ > owner@:--------------:-------:deny > owner@:rwxp---A-W-Co-:-------:allow > group@:-w-p----------:-------:deny > group@:r-x-----------:-------:allow > everyone@:-w-p---A-W-Co-:-------:deny > everyone@:r-x---a-R-c--s:-------:allow > bash-3.2# ls -Vd pardatapool/fs2/fs2_sub/ > drwxr-xr-x 2 remcol root 2 Nov 1 14:22 > pardatapool/fs2/fs2_sub/ > owner@:--------------:-------:deny > owner@:rwxp---A-W-Co-:-------:allow > group@:-w-p----------:-------:deny > group@:r-x-----------:-------:allow > everyone@:-w-p---A-W-Co-:-------:deny > everyone@:r-x---a-R-c--s:-------:allow > bash-3.2# > > Thanks, > > ..Remco > >> Also please post the following information: >> >> - The user you're logged in on your Windows client >> - Output of "ls -Vd" for pardatapool, fs2, and fs2_sub >> >> Thanks, >> Afshin >> >> Afshin Salek wrote: >>> please run and post the output of the following script so that >>> I can take a look at your configuration: >>> >>> http://opensolaris.org/os/project/cifs-server/files/cifs-gendiag >>> >>> Afshin >>> >>> Remco Lengers wrote: >>>> Afshin, All, >>>> >>>> The example below demonstrates the issue. I don't think there is a >>>> permission problem: >>>> >>>> >>>> C:\Documents and Settings\remcol> >>>> C:\Documents and Settings\remcol>net use L: \\par\myshare >>>> The command completed successfully. >>>> >>>> >>>> C:\Documents and Settings\remcol>net use >>>> New connections will be remembered. >>>> >>>> >>>> Status Local Remote Network >>>> >>>> ------------------------------------------------------------------------------- >>>> OK L: \\par\myshare Microsoft Windows >>>> Network >>>> The command completed successfully. >>>> >>>> C:\Documents and Settings\remcol>dir l:\ >>>> Volume in drive L is pardatapool >>>> Volume Serial Number is C4BA-C348 >>>> >>>> Directory of l:\ >>>> >>>> 31-10-2008 21:06 <DIR> . >>>> 31-10-2008 19:20 <DIR> .. >>>> 31-10-2008 19:21 <DIR> fs2_sub >>>> 0 File(s) 0 bytes >>>> 3 Dir(s) 776.689.580.544 bytes free >>>> >>>> C:\Documents and Settings\remcol>dir l:\fs2_sub >>>> Volume in drive L is pardatapool >>>> Volume Serial Number is C4BA-C348 >>>> >>>> Directory of l:\fs2_sub >>>> >>>> File Not Found >>>> >>>> C:\Documents and Settings\remcol>copy c:\autoexec.bat l:\ >>>> 1 file(s) copied. >>>> >>>> C:\Documents and Settings\remcol>copy c:\autoexec.bat l:\fs2_sub\ >>>> Access is denied. >>>> 0 file(s) copied. >>>> >>>> C:\Documents and Settings\remcol> >>>> C:\Documents and Settings\remcol>net use k: \\par\myshare_fs2_sub >>>> The command completed successfully. >>>> >>>> >>>> C:\Documents and Settings\remcol>copy c:\autoexec.bat k:\ >>>> 1 file(s) copied. >>>> >>>> >>>> C:\Documents and Settings\remcol>net use >>>> New connections will be remembered. >>>> >>>> >>>> Status Local Remote Network >>>> >>>> ------------------------------------------------------------------------------- >>>> OK K: \\PAR\MYSHARE_FS2_SUB Microsoft Windows >>>> Network >>>> OK L: \\par\myshare Microsoft Windows >>>> Network >>>> The command completed successfully. >>>> >>>> >>>> C:\Documents and Settings\remcol> >>>> >>>> Regards, >>>> >>>> ..Remco >>>> >>>> Afshin Salek wrote: >>>>> The example in the manual is not pointless but it assumes that >>>>> you set the permissions in a way that gives access to connected >>>>> users and that's basically part of your file system settings >>>>> rather than CIFS configuration. >>>>> >>>>> Does the connected user has enough access permissions on fs2_sub? >>>>> >>>>> Afshin >>>>> >>>>> [EMAIL PROTECTED] wrote: >>>>>> Hi Afshin, All, >>>>>> >>>>>> Thanks for that. Just for my sanity. If I read the CR it look like >>>>>> something much more complex that I am actually trying to do. >>>>>> Basically I >>>>>> am just following the example in the manual here: >>>>>> >>>>>> http://docs.sun.com/app/docs/doc/820-2429/createstaticsmbsharezfstask?a=view >>>>>> >>>>>> >>>>>> # zfs create -o casesensitivity=mixed -o nbmand=on pardatapool/fs2 >>>>>> # zfs set sharesmb=name=myshare pardatapool/fs2 >>>>>> # sharemgr show -vp >>>>>> default nfs=() >>>>>> /pardatapool/incoming "" >>>>>> zfs >>>>>> zfs/pardatapool/fs2 smb=() >>>>>> myshare=/pardatapool/fs2 >>>>>> # zfs create -o casesensitivity=mixed -o nbmand=on >>>>>> pardatapool/fs2/fs2_sub >>>>>> # sharemgr show -vp >>>>>> default nfs=() >>>>>> /pardatapool/incoming "" >>>>>> zfs >>>>>> zfs/pardatapool/fs2 smb=() >>>>>> myshare=/pardatapool/fs2 >>>>>> myshare_fs2_sub=/pardatapool/fs2/fs2_sub >>>>>> # >>>>>> >>>>>> And this already cause a "Access denied" when accessing "fs2_sub" on >>>>>> the >>>>>> windows client. Is the example in the manual just pointless? >>>>>> >>>>>> Thanks in advice, >>>>>> >>>>>> ..Remco >>>>>> >>>>>>> You can monitor 6711751 bug ID in bugs.opensolaris.org >>>>>>> >>>>>>> There is no PSARC case yet but we might need to file one >>>>>>> to get some support from ZFS for DFS links. We will know >>>>>>> when we start the design phase. >>>>>>> >>>>>>> Afshin >>>>>>> >>>>>>> Remco Lengers wrote: >>>>>>>> All, >>>>>>>> >>>>>>>> Any idea when " the Solaris SMB server gets support for DFS"? Any >>>>>>>> where >>>>>>>> that I can follow the development? Any PSARC case that I can >>>>>>>> follow? >>>>>>>> >>>>>>>> ..Remco >>>>>>>> >>>>>>>> The answer to my original question was: >>>>>>>> >>>>>>>> ------ >>>>>>>> True, there's no mount-point crossing, but Windows/CIFS does >>>>>>>> support DFS >>>>>>>> referrals. The Solaris SMB server does not support DFS yet though. >>>>>>>> >>>>>>>> So you're correct: shared nested filesystems on the server side do >>>>>>>> not >>>>>>>> look like that on the client side. When the Solaris SMB server >>>>>>>> gets >>>>>>>> support for DFS then this situation will change. >>>>>>>> ------ >>>>>>>> >>>>>>>> My original question was: >>>>>>>> >>>>>>>> ------ >>>>>>>> >>>>>>>> please reply to me directly as well. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> I am migrating from my "old" sb100 S10 U2 home server to a new AMD >>>>>>>> x64 >>>>>>>> >>>>>>>> Nevada build 100 server. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On my old server I had zfs fileystems like so: >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> metronpool/dump/fotos 60.6G 13.3G 36.5K /metronpool/dump/fotos >>>>>>>> metronpool/dump/fotos/2000 319M 13.3G 319M >>>>>>>> /metronpool/dump/fotos/2000 >>>>>>>> metronpool/dump/fotos/2001 885M 13.3G 885M >>>>>>>> /metronpool/dump/fotos/2001 >>>>>>>> >>>>>>>> ..... >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> And then I had metronpool/dump/fotos shared with SAMBA to my PC's. >>>>>>>> This >>>>>>>> meant that all file systems under ../foto/.. were accessible just >>>>>>>> fine. >>>>>>>> It allowed me to access all filesystems via a single samba share. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Now I am trying to set that up with Nevada, moving over and >>>>>>>> upgrading >>>>>>>> the zfs snapshots no problem >>>>>>>> >>>>>>>> pardatapool/export/fotos 60.4G 723G 29K >>>>>>>> /pardatapool/export/fotos >>>>>>>> pardatapool/export/fotos/2000 319M 723G 318M >>>>>>>> /pardatapool/export/fotos/2000 >>>>>>>> pardatapool/export/fotos/2001 886M 723G 885M >>>>>>>> /pardatapool/export/fotos/2001 >>>>>>>> >>>>>>>> zfs set sharesmb=on pardatapool/export/foto >>>>>>>> >>>>>>>> # sharemgr show >>>>>>>> >>>>>>>> default >>>>>>>> >>>>>>>> zfs >>>>>>>> >>>>>>>> zfs/pardatapool/export/fotos >>>>>>>> /pardatapool/export/fotos >>>>>>>> /pardatapool/export/fotos/2000 >>>>>>>> /pardatapool/export/fotos/2001 >>>>>>>> >>>>>>>> # >>>>>>>> >>>>>>>> All looks fine however when I try to access the smb share on my >>>>>>>> pc's I >>>>>>>> get "access or permission denied" when wanting to access the 2000 >>>>>>>> and >>>>>>>> 2001 "directories". >>>>>>>> >>>>>>>> Any idea what I am doing wrong? >>>>>>>> >>>>>>>> ------ >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> cifs-discuss mailing list >>>>>>>> [email protected] >>>>>>>> http://mail.opensolaris.org/mailman/listinfo/cifs-discuss >>>>>>> _______________________________________________ >>>>>>> cifs-discuss mailing list >>>>>>> [email protected] >>>>>>> http://mail.opensolaris.org/mailman/listinfo/cifs-discuss >>>>>>> >>>>>> _______________________________________________ >>>>>> cifs-discuss mailing list >>>>>> [email protected] >>>>>> http://mail.opensolaris.org/mailman/listinfo/cifs-discuss >>>> _______________________________________________ >>>> cifs-discuss mailing list >>>> [email protected] >>>> http://mail.opensolaris.org/mailman/listinfo/cifs-discuss >>> _______________________________________________ >>> cifs-discuss mailing list >>> [email protected] >>> http://mail.opensolaris.org/mailman/listinfo/cifs-discuss _______________________________________________ cifs-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
