Reginald Beardsley wrote: > Well, not quite. Look at my more recent post. I'm not yet 100% sure of the > details, but it revolves around how zfs & be interact. And most likely the > namespace collision between rpool & fpool. However, you can see & manipulate > things w/ beadm that you can't access w/ zfs. > > There are doubtless sound reasons for this hidden in the implementation > details. > > fpool was mounted under /mnt, it just wasn't the portion of fpool I wanted > to access. My observation of df over the past few years is that it doesn't > quite grok zfs yet. I find myself using "zfs list" quite a bit. > > In any event, the confluence of comments got me to the solution. Which is > what matters.
None of that rings true to me, but if it's working for you, that's great. -- James Carlson 42.703N 71.076W <carls...@workingcode.com> _______________________________________________ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
