[OpenIndiana-discuss] Access to /etc on a pool from another system?
Reginald Beardsley
pulaskite at yahoo.com
Mon Mar 19 21:16:39 UTC 2012
I would expect /mnt to contain /mnt/etc also.
rhb at openindiana:~# df /mnt
/ (rpool/ROOT/oi_151 ):360070851 blocks 360070851 files
rhb at openindiana:~#
There's nothing particularly odd about the /mnt/fpool.
This is the "zfs list" entry for /rpool
rpool 56.7G 172G 45.5K /rpool
So w/ fpool mounted on /mnt instead of / everything is as normal. The contents of /mnt/fpool are exactly what you find in /rpool
There were no errors that I recall other than fat fingers.
zfs treats / specially. I ran into this last year about this time when trying to clone the same install of Solaris 10 u8 onto an HP z400 & a f700 laptop. Finally gave up after almost 3 weeks. There's probably a way to do it, but every way I found I encountered "you can't get there from here" which was a real surprise as I've always been able to do this w/ ufs.
Doing the obvious:
boot from a USB drive image
create filesystem on target
copy filesystem contents fomr baseline
failed no matter what I tried. zfs send, flar, tar & cpio.
Now that I think about it, the problems seemed to revolve around the special way that zfs and beadm treat /.
Just to be sure I just ran a scrub on fpool.
rhb at openindiana:~# zpool status fpool
pool: fpool
state: ONLINE
scan: scrub repaired 0 in 0h9m with 0 errors on Tue Mar 20 05:08:56 2012
config:
NAME STATE READ WRITE CKSUM
fpool ONLINE 0 0 0
c0t0d0s0 ONLINE 0 0 0
errors: No known data errors
I've imported and exported fpool quite a few times now w/o problems
--- On Mon, 3/19/12, James Carlson <carlsonj at workingcode.com> wrote:
> From: James Carlson <carlsonj at workingcode.com>
> Subject: Re: [OpenIndiana-discuss] Access to /etc on a pool from another system?
> To: "Discussion list for OpenIndiana" <openindiana-discuss at openindiana.org>
> Date: Monday, March 19, 2012, 1:45 PM
> Reginald Beardsley wrote:
> > This is in response to all.
> >
> > rhb at openindiana:~# zfs list -r fpool
> > NAME
> USED AVAIL
> REFER MOUNTPOINT
> > fpool
> 6.97G 105G
> 45K /mnt/fpool
> > fpool/ROOT
> 3.72G 105G 31K
> legacy
> > fpool/ROOT/openindiana
> 3.72G 105G 3.60G /mnt
> > fpool/dump
> 479M 105G 479M
> -
> > fpool/export
> 2.24G 105G 32K
> /mnt/export
> > fpool/export/home
> 2.24G 105G
> 32K /mnt/export/home
> >
> fpool/export/home/rhb 2.24G 105G
> 2.24G /mnt/export/home/rhb
> > fpool/swap
> 544M 105G 523M
> -
>
> What does "df /mnt" say?
>
> With that layout, I'd expect /mnt/etc to contain the "/etc"
> from that
> system.
>
> If it doesn't, then perhaps it's as simple as the strange
> "/mnt/fpool"
> entry causing the "/mnt" mount to fail.
>
> Where there errors when you mounted these file
> systems? Perhaps one
> saying that the system was unable to mount
> fpool/ROOT/openindiana
> because the "/mnt" directory was not empty?
>
> --
> James Carlson 42.703N
> 71.076W <carlsonj at workingcode.com>
>
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
>
More information about the OpenIndiana-discuss
mailing list