On Wed, Oct 1, 2008 at 3:42 AM, Douglas R. Jones <[EMAIL PROTECTED]> wrote: ... > 3) Next I created another file system called dpool/GroupWS/Integration. Its > mount point was inherited from GroupWS and is /mnt/zfs1/GroupWS/Integration. > Essentially I only allowed the new file system to inherit from its parent. > 4) I change the auto.ws map thusly: > Integration chekov:/mnt/zfs1/GroupWS/& > Upgrades chekov:/mnt/zfs1/GroupWS/& > cstools chekov:/mnt/zfs1/GroupWS/& > com chekov:/mnt/zfs1/GroupWS > > Now the odd behavior. You will notice that the directories Upgrades and > cstools are just that. Directories in GroupWS. You can cd /ws/cstools from > [b][i]any server[/b][/i] without a problem. Perform and ls and you see what > you expect to see. Now the rub. If on chekov, one does a cd /ws/Integration > you end up in chekov:/mnt/zsf1/GroupWS/Integration and everything is great. > Do a cd to /ws/com and everything is fine. You can do a cd to Integration and > everything is fine. But. If you go to another server and do a cd > /ws/Integration all is well. However, if you do a cd to /ws/com and then a cd > Integration, Integration is EMPTY!! > > Any ideas?
Well, I guess you're running Solaris 10 and not OpenSolaris/SXCE. I think the term is mirror mounts. It works just fine on my SXCE boxes. Until then, the way we got round this was to not make the new filesystem a child. So instead of: /mnt/zfs1/GroupWS /mnt/zfs1/GroupWS/Integration create /mnt/zfs1/GroupWS /mnt/zfs1/Integration and use that for the Integration mountpoint. Then in GroupWS, 'ln -s ../Integration .'. That way, if you look at Integration in /ws/com you get to something that exists. -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
