Harry Putnam
2014-04-02 02:45:49 UTC
There are numerous sites online explaining how to mirror rpool, but
after looking at a few I've noticed they all seem to have what appears
(to me) to be a common shortcomming.
In each case extraneous suffixes start to appear at the end of the
disk names with no explanation about where they come from.
They all tell you to use format to find the disk names but then
proceed names that are different than those shown with format.
At least the docs at openindiana wiki explain one of the suffixes
('p0').
(http://wiki.openindiana.org/oi/2.1+Post-installation)
So at the point we are shown how to streamline fdisking a partition
with:
pfexec fdisk -B c3t1d0p0 (p0 is the whole disk starting from
the MBR)
They explain where p0 came from
But then in the very next step where they start to tell you how to
label the disk suddenly the disc name has grown an 's2' on the end.
Now we set up an SMI label with same partitioning as disk 0 on disk 1.
# pfexec prtvtoc /dev/rdsk/c3t0d0s2 |
pfexec fmthard -s - /dev/rdsk/c3t1d0s2
No mention at all where s2 comes from, certainly not from looking at
the output of format.
Next step has the discs growing yet a different suffix (s0):
Now we add the 2nd drive to our rpool by issuing:
# pfexec zpool attach -f rpool c3t0d0s0 c3t1d0s0
Again no explanation at all about where 's0' comes from.
When I try these steps I get errors about not finding such discs or
not being able to use an efi labeled disk...
I'm not sure if the suffix is to blame or what.
I'm guessing it might be something like s2 for solaris2 and s0
indicating the whole disk is for solaris but that is just guess work.
1) So what is going with those changing names?
2) Should I be able to use the steps shown there just as they are
(including unexplained suffixes) if I insert the basename of the
discs I'm using?
( I asked the second part above because some of the solaris type
documentation is very old, this is less than 3 yrs old so I guess it
should still be accurate but I'm not really sure).
after looking at a few I've noticed they all seem to have what appears
(to me) to be a common shortcomming.
In each case extraneous suffixes start to appear at the end of the
disk names with no explanation about where they come from.
They all tell you to use format to find the disk names but then
proceed names that are different than those shown with format.
At least the docs at openindiana wiki explain one of the suffixes
('p0').
(http://wiki.openindiana.org/oi/2.1+Post-installation)
So at the point we are shown how to streamline fdisking a partition
with:
pfexec fdisk -B c3t1d0p0 (p0 is the whole disk starting from
the MBR)
They explain where p0 came from
But then in the very next step where they start to tell you how to
label the disk suddenly the disc name has grown an 's2' on the end.
Now we set up an SMI label with same partitioning as disk 0 on disk 1.
# pfexec prtvtoc /dev/rdsk/c3t0d0s2 |
pfexec fmthard -s - /dev/rdsk/c3t1d0s2
No mention at all where s2 comes from, certainly not from looking at
the output of format.
Next step has the discs growing yet a different suffix (s0):
Now we add the 2nd drive to our rpool by issuing:
# pfexec zpool attach -f rpool c3t0d0s0 c3t1d0s0
Again no explanation at all about where 's0' comes from.
When I try these steps I get errors about not finding such discs or
not being able to use an efi labeled disk...
I'm not sure if the suffix is to blame or what.
I'm guessing it might be something like s2 for solaris2 and s0
indicating the whole disk is for solaris but that is just guess work.
1) So what is going with those changing names?
2) Should I be able to use the steps shown there just as they are
(including unexplained suffixes) if I insert the basename of the
discs I'm using?
( I asked the second part above because some of the solaris type
documentation is very old, this is less than 3 yrs old so I guess it
should still be accurate but I'm not really sure).