[OpenIndiana-discuss] Replacing smaller rpool SSD with bigger one - best praxis

[gea]

I suppose a method based on mirror/clone + autoexpand will not work with 
different ashift.

A disaster backup/recovery method that should work:
- replicate current BE to datapool via zfs send
   (you can create daily recoverable backups while OI is running with 
this method)
- do a minimal setup of OI on the new disk
- replicate BE back to rpool/ROOT
- activate this BE and reboot

gea

Am 07.03.2023 um 20:39 schrieb Predrag Zečević via openindiana-discuss:
> Hi all,
>
> I did my homework, and was browsing forums/internet for proper 
> solution. Seems, I could not find it.
>
> Right now, I have rpool consisting from single SSD (250GB):
>
> ---8<------
>
> :; pfexec fdisk /dev/rdsk/c2t0d0p0
>              Total disk size is 38934 cylinders
>              Cylinder size is 12544 (512 byte) blocks
>
>                                                Cylinders
>       Partition   Status    Type          Start   End   Length %
>       =========   ======    ============  =====   ===   ====== ===
>           1       Active    Solaris2          1  28081 28081 72
>           2                 Linux native   28081  29752 1672 4
>           3                 Linux native   29753  38934 9182 24
> ---8<------
> Partitions 2 and 3 are used for zfs caches (ZIL and ARC)
>
> It was created long time ago, and zdb shows "ashift = 9" on it.
>
>
> Now, I want to replace it with another SSD (500GB), with similar 
> partitioning (e.g. Solaris 2 partition for rpool, partitions 2 and 3 
> for cache devices -- with adjusted values, of course) -- but with 
> "ashift = 12" set.
>
>
> What would be the best approach to achieve that (beside creating new 
> pool, and using zfs send/recv)?
>
> Thanks in advance.
>
>
> P.S: cache devices are used by another pool (located on HDD), to 
> speed-up its use
>
> P.P.S: I apologize if I missed some (on the net) available documentation. 

-- 
Guenther Alka
Rektor-Klaus Str. 71
73525 Schw. Gmünd

gea at napp-it.org


-- 
Diese E-Mail wurde von AVG-Antivirussoftware auf Viren geprüft.
www.avg.com