zfs discuss - Oct 2008 - Root pool mirror wasn''t automatically configured during install

Is the following issue related to (will probably get fixed by) 
bug 6748133? ...

During a net-install of b96, I modified the name of the root pool,
overriding the default name, rpool. After the install, the pool was on
a single device instead of mirrored on two devices, and doing a manual
zpool attach was required.

-Eric

Hi Eric,

Are you saying that you selected two-disks for a mirrored root pool
during the initial install and because you changed the default
rpool name, the pool was created with just one disk?

I netinstalled build 96, selected two disks for the root pool mirror,
backspaced over "rpool" with "mypool" and still ended up
with a 2-disk
mirrored root pool named mypool.

Are you sure that you selected a two-disk mirror during the initial
install of build 96?

See the output below.

Cindy

Preparing system for Solaris install

Configuring disk (c0t0d0)
         - Creating Solaris disk label (VTOC)

Configuring disk (c0t1d0)
         - Creating Solaris disk label (VTOC)
         - Creating pool mypool
         - Creating swap zvol for pool mypool
         - Creating dump zvol for pool mypool
.
.
.

Cleaning devices

Customizing system devices
         - Physical devices (/devices)
         - Logical devices (/dev)

Installing boot information
         - Installing boot blocks (c0t1d0s0)
         - Installing boot blocks (/dev/rdsk/c0t0d0s0)
         - Installing boot blocks (/dev/rdsk/c0t1d0s0)

# zpool status
   pool: mypool
  state: ONLINE
  scrub: none requested
config:

         NAME          STATE     READ WRITE CKSUM
         mypool        ONLINE       0     0     0
           mirror      ONLINE       0     0     0
             c0t0d0s0  ONLINE       0     0     0
             c0t1d0s0  ONLINE       0     0     0

errors: No known data errors



Eric Boutilier wrote:
> Is the following issue related to (will probably get fixed by) 
> bug 6748133? ...
> 
> During a net-install of b96, I modified the name of the root pool,
> overriding the default name, rpool. After the install, the pool was on
> a single device instead of mirrored on two devices, and doing a manual
> zpool attach was required.
> 
> -Eric
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

On Fri, 3 Oct 2008, Cindy.Swearingen at Sun.COM wrote:
> Eric Boutilier wrote:
>> Is the following issue related to (will probably get fixed by) bug
6748133?
>> ...
>> 
>> During a net-install of b96, I modified the name of the root pool,
>> overriding the default name, rpool. After the install, the pool was on
>> a single device instead of mirrored on two devices, and doing a manual
>> zpool attach was required.
>> 
>
> Hi Eric,
>
> Are you saying that you selected two-disks for a mirrored root pool
> during the initial install and because you changed the default
> rpool name, the pool was created with just one disk?
>
>    I netinstalled build 96, selected two disks for the root pool mirror,
>    backspaced over "rpool" with "mypool" and still
ended up with a 2-disk
>    mirrored root pool named mypool.
>
> Are you sure that you selected a two-disk mirror during the initial
> install of build 96?
>
> See the output below.
>
> Cindy
>
> Preparing system for Solaris install
>
> Configuring disk (c0t0d0)
>        - Creating Solaris disk label (VTOC)
>
> Configuring disk (c0t1d0)
>        - Creating Solaris disk label (VTOC)
>        - Creating pool mypool
>        - Creating swap zvol for pool mypool
>        - Creating dump zvol for pool mypool
> .
> .
> .
>
> Cleaning devices
>
> Customizing system devices
>        - Physical devices (/devices)
>        - Logical devices (/dev)
>
> Installing boot information
>        - Installing boot blocks (c0t1d0s0)
>        - Installing boot blocks (/dev/rdsk/c0t0d0s0)
>        - Installing boot blocks (/dev/rdsk/c0t1d0s0)
>
> # zpool status
>  pool: mypool
> state: ONLINE
> scrub: none requested
> config:
>
>        NAME          STATE     READ WRITE CKSUM
>        mypool        ONLINE       0     0     0
>          mirror      ONLINE       0     0     0
>            c0t0d0s0  ONLINE       0     0     0
>            c0t1d0s0  ONLINE       0     0     0
>
> errors: No known data errors
>
Cindy,

Thanks for the reply -- I retraced my steps, and I''m now convinced it
was indeed pilot error. I went back through the install screens (I''m
still getting used to the new screens -- also, we''re doing remote
console based installs), and apparently on the one that says to select
multiple disks if you want mirroring, I simply F2''d right past it.  :-)

Then when I went to rectify the situation (make it mirrored by doing a
zpool attach manually), it told me to use -f because the slice belonged
to "rpool". I now realize that was probably a vestige of a previous
install, not something that happened behind the scenes during this install.

Thank you!
Eric