Jim Klimov writes: > It creates mountpoints for my ZFS hierarchy, even though it doesn't mount the > filesystems.
Did you upgrade the LU packages to the newest versions before creating the new BE? For what it's worth, this sounds like CR 6376420, an old problem. > For example, my distribution ISO images are in pool/export/ftp > ZFS tree, where pool/export is explicitly mounted as /export and > pool/export/ftp > inherits a mountpoint as /export/ftp. Yep; that'll trigger the above bug. > I wonder if this blatant creation of the tree of mountpoints can be disabled > for > good? I tried removing them all, but they re-appear on next lumount. lumount shouldn't create these things; I don't know of any cases where that happens. lucreate and lumake do create them, though, so after an upgrade, it's sufficient to mount up the new boot environment once and rmdir the stray mount points. Yes, ZFS does insist on non-empty status, and it does so on all versions. It's an intentional feature. (I haven't seen this LU bug in quite a while ... but then I switched over to a ZFS root some time ago.) -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
