beadm is missing a qualifier on mount to specify the pool name under which the named BE is located, so it mounts the first BE it finds with the name you specify. Since you had the same BE name present in your existing root pool, that gets in the way. Your workaround removed the conflict and that's why it worked.

Dave

On 03/19/12 23:18, 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.

So thanks again to all.

Have Fun!
Reg


--- On Mon, 3/19/12, James Carlson<carls...@workingcode.com>  wrote:

From: James Carlson<carls...@workingcode.com>
Subject: Re: [OpenIndiana-discuss] Access to /etc on a pool from another system?
To: openindiana-discuss@openindiana.org
Date: Monday, March 19, 2012, 8:15 PM
On 03/19/12 17:16, Reginald Beardsley
wrote:
I would expect /mnt to contain /mnt/etc also.

rhb@openindiana:~# df /mnt
/� � � � � � �
� � (rpool/ROOT/oi_151 ):360070851 blocks
360070851 files
rhb@openindiana:~#

Well, there's your problem.� /mnt isn't mounted.�
All you're looking at
is your native rpool root file system, not the one in
fpool.

Now that I think about it, the problems seemed to
revolve around the special way that zfs and beadm treat /.

Other than being "canmount=no", it's not too special.�
Just look at the
ZFS attributes; they tell you everything you might want to
know.

zfs get -o all all fpool/ROOT/opensolaris

--
James Carlson� � � ���42.703N
71.076W� � � ���<carls...@workingcode.com>

_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss


_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss


_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Reply via email to