Not sure if this is a bug, or desired behavior, but it doesn''t seem right to me, and a possible admin headache. bash-3.00# zfs create pool/test2 bash-3.00# zfs create pool/test2/blah on another box, in this case it was a linux box. mount the first filesystem. [root at localhost systemtap]# mount 192.168.1.16:/pool/test2 [root at localhost systemtap]# mkdir /t2/blah mkdir: cannot create directory `/t2/blah'': File exists as expected. it wont allow the dir to be created, now the problem [root at localhost systemtap]# cd /t2 [root at localhost t2]# ls blah [root at localhost t2]# cd blah [root at localhost blah]# ls [root at localhost blah]# touch test okay now on the solaris box. bash-3.00# cd /pool/test2 bash-3.00# ls blah bash-3.00# cd blah bash-3.00# ls bash-3.00# no file was created. destroy the pool bash-3.00# zfs destroy -f pool/test2/blah bash-3.00# cd /pool/test2/ bash-3.00# ls blah there is the missing file, the nfs mounted filesystem didn''t follow into the other zfs filesystem.