SOLVED Boot Vol upgrade: autoexpand?

[depasseg]

I currently have mirrored USB sticks for my boot volume.
I just ordered 2 DOM's to replace the USB's.
In order to keep my previous boot volumes, I would like to add the 2 DOM's to the Boot volume, and then remove the 2 USB's.
Since the DOM's are larger than the USB's, what happens to the excess space? I would like to be able to use all the DOM space.

Thx!

 

[Bidule0hm]

Or just re-install and import the config :)

 

[gpsguy]

I think you could replace them one at a time, just like one would do for an in place upgrade to larger drives.


Sent from my iPhone using Tapatalk

 

[depasseg]

Or just re-install and import the config :)

That doesn't keep the boot environment snapshots, does it?

 

[Bidule0hm]

Nop.

 

[gpsguy]

That's why I suggested the other route.


Sent from my iPhone using Tapatalk

 

[Mlovelace]

I currently have mirrored USB sticks for my boot volume.
I just ordered 2 DOM's to replace the USB's.
In order to keep my previous boot volumes, I would like to add the 2 DOM's to the Boot volume, and then remove the 2 USB's.
Since the DOM's are larger than the USB's, what happens to the excess space? I would like to be able to use all the DOM space.

Thx!

Looks like the boot pool isn't set to autoexpand:

Code:

zpool get autoexpand
NAME          PROPERTY    VALUE   SOURCE
freenas-boot  autoexpand  off     default

Just set the autoexpand to on before you swap the boot devices.

 

[depasseg]

Looks like the boot pool isn't set to autoexpand:

Code:

zpool get autoexpand
NAME          PROPERTY    VALUE   SOURCE
freenas-boot  autoexpand  off     default

Just set the autoexpand to on before you swap the boot devices.

Nice! Thx!!

 

[cyberjock]

The autoexpand is off because (if memory serves me right) the boot manager (g-something.. I'm tired) doesn't handle autoexpanded zpools very well.

If you want to go to a bigger zpool I think the only option is to simply do a fresh install on the new disks, then import your config file.

 

[depasseg]

The autoexpand is off because (if memory serves me right) the boot manager (g-something.. I'm tired) doesn't handle autoexpanded zpools very well.

If you want to go to a bigger zpool I think the only option is to simply do a fresh install on the new disks, then import your config file.

That's what I feared, so I'm going to test it in a VM and see how it goes.

 

[Mlovelace]

The autoexpand is off because (if memory serves me right) the boot manager (g-something.. I'm tired) doesn't handle autoexpanded zpools very well.

Grub.

Good to know, thanks!


Edit: worth a read ;) https://bugs.pcbsd.org/issues/7314

 

[depasseg]

Very interesting bug report and oracle docs. Looks like it's possible to move to the bigger devices, then either set autoexpand=on (temporarily to expand then set to off), or zpool online -e.
http://docs.oracle.com/cd/E19253-01/819-5461/githb/index.html

 

[zambanini]

just an idea: dd one of your sticks to a bigger one, then expand it.

 

[cyberjock]

Very interesting bug report and oracle docs. Looks like it's possible to move to the bigger devices, then either set autoexpand=on (temporarily to expand then set to off), or zpool online -e.
http://docs.oracle.com/cd/E19253-01/819-5461/githb/index.html

Since Oracle's code is several years apart from the OpenZFS project, I wouldn't trust that it is 100% correct until someone actually verifies the behavior. Any documentation from Oracle should be assumed to be "incorrect" until proven otherwise to be on the conservative side.

 

[depasseg]

Since Oracle's code is several years apart from the OpenZFS project, I wouldn't trust that it is 100% correct until someone actually verifies the behavior. Any documentation from Oracle should be assumed to be "incorrect" until proven otherwise to be on the conservative side.

Good point! I'm basing it more on the bug report response from Josh (who assessed the Oracle doc). But I'll be trying it in a test system first.

 

[cyberjock]

Yeah, that's also a year old. Oracle could have changed things since then. I'm not saying its not correct (frankly, I think that it is correct). BUT... I always validate that something works from Oracle docs before I link to it. And if I can find a better reference, I link to that instead. ;)

 

[depasseg]

Sweet! It worked! Hello mirrored 128GB m.sata's!

Code:

[root@freenas1] ~# zpool status freenas-boot
  pool: freenas-boot
state: ONLINE
  scan: resilvered 43.7G in 0h16m with 0 errors on Fri Apr  8 19:04:47 2016
config:

        NAME        STATE     READ WRITE CKSUM
        freenas-boot  ONLINE       0     0     0
          mirror-0  ONLINE       0     0     0
            ada2p2  ONLINE       0     0     0
            ada3p2  ONLINE       0     0     0

errors: No known data errors
[root@freenas1] ~# zpool set autoexpand=on freenas-boot
[root@freenas1] ~# zfs list freenas-boot
NAME           USED  AVAIL  REFER  MOUNTPOINT
freenas-boot  21.9G  6.96G    31K  none
[root@freenas1] ~# zpool offline freenas-boot ada2p2
[root@freenas1] ~# zpool online -e freenas-boot ada2p2
[root@freenas1] ~# zpool offline freenas-boot ada3p2
[root@freenas1] ~# zpool online -e freenas-boot ada3p2
[root@freenas1] ~# zpool status freenas-boot
  pool: freenas-boot
state: ONLINE
  scan: resilvered 386K in 0h0m with 0 errors on Sat Apr  9 18:47:37 2016
config:

        NAME        STATE     READ WRITE CKSUM
        freenas-boot  ONLINE       0     0     0
          mirror-0  ONLINE       0     0     0
            ada2p2  ONLINE       0     0     0
            ada3p2  ONLINE       0     0     0

errors: No known data errors
[root@freenas1] ~# zfs list freenas-boot
NAME           USED  AVAIL  REFER  MOUNTPOINT
freenas-boot  21.9G  86.4G    31K  none
[root@freenas1] ~# zpool set autoexpand=off freenas-boot
[root@freenas1] ~# 

 

[ovizii]

Sweet! It worked! Hello mirrored 128GB m.sata's!

Code:

[root@freenas1] ~# zpool status freenas-boot
  pool: freenas-boot
state: ONLINE
  scan: resilvered 43.7G in 0h16m with 0 errors on Fri Apr  8 19:04:47 2016
config:

        NAME        STATE     READ WRITE CKSUM
        freenas-boot  ONLINE       0     0     0
          mirror-0  ONLINE       0     0     0
            ada2p2  ONLINE       0     0     0
            ada3p2  ONLINE       0     0     0

errors: No known data errors
[root@freenas1] ~# zpool set autoexpand=on freenas-boot
[root@freenas1] ~# zfs list freenas-boot
NAME           USED  AVAIL  REFER  MOUNTPOINT
freenas-boot  21.9G  6.96G    31K  none
[root@freenas1] ~# zpool offline freenas-boot ada2p2
[root@freenas1] ~# zpool online -e freenas-boot ada2p2
[root@freenas1] ~# zpool offline freenas-boot ada3p2
[root@freenas1] ~# zpool online -e freenas-boot ada3p2
[root@freenas1] ~# zpool status freenas-boot
  pool: freenas-boot
state: ONLINE
  scan: resilvered 386K in 0h0m with 0 errors on Sat Apr  9 18:47:37 2016
config:

        NAME        STATE     READ WRITE CKSUM
        freenas-boot  ONLINE       0     0     0
          mirror-0  ONLINE       0     0     0
            ada2p2  ONLINE       0     0     0
            ada3p2  ONLINE       0     0     0

errors: No known data errors
[root@freenas1] ~# zfs list freenas-boot
NAME           USED  AVAIL  REFER  MOUNTPOINT
freenas-boot  21.9G  86.4G    31K  none
[root@freenas1] ~# zpool set autoexpand=off freenas-boot
[root@freenas1] ~# 

I can confirm, that worked flawless for me too!

 

[aookeopinetree]

Sweet! It worked! Hello mirrored 128GB m.sata's!

Code:

[root@freenas1] ~# zpool status freenas-boot
  pool: freenas-boot
state: ONLINE
  scan: resilvered 43.7G in 0h16m with 0 errors on Fri Apr  8 19:04:47 2016
config:

        NAME        STATE     READ WRITE CKSUM
        freenas-boot  ONLINE       0     0     0
          mirror-0  ONLINE       0     0     0
            ada2p2  ONLINE       0     0     0
            ada3p2  ONLINE       0     0     0

errors: No known data errors
[root@freenas1] ~# zpool set autoexpand=on freenas-boot
[root@freenas1] ~# zfs list freenas-boot
NAME           USED  AVAIL  REFER  MOUNTPOINT
freenas-boot  21.9G  6.96G    31K  none
[root@freenas1] ~# zpool offline freenas-boot ada2p2
[root@freenas1] ~# zpool online -e freenas-boot ada2p2
[root@freenas1] ~# zpool offline freenas-boot ada3p2
[root@freenas1] ~# zpool online -e freenas-boot ada3p2
[root@freenas1] ~# zpool status freenas-boot
  pool: freenas-boot
state: ONLINE
  scan: resilvered 386K in 0h0m with 0 errors on Sat Apr  9 18:47:37 2016
config:

        NAME        STATE     READ WRITE CKSUM
        freenas-boot  ONLINE       0     0     0
          mirror-0  ONLINE       0     0     0
            ada2p2  ONLINE       0     0     0
            ada3p2  ONLINE       0     0     0

errors: No known data errors
[root@freenas1] ~# zfs list freenas-boot
NAME           USED  AVAIL  REFER  MOUNTPOINT
freenas-boot  21.9G  86.4G    31K  none
[root@freenas1] ~# zpool set autoexpand=off freenas-boot
[root@freenas1] ~# 

Heya, would you be able to write a guide of what you did to turn autoexpand on and the order that you did each step? I wish to do something like this to move my current OS installation onto bigger storage space without losing my current snapshots.

Are your m.sata drives directly connected to the motherboard or in a usb enclosure?

 

[depasseg]

I'll try to remember what I did. I think I just replaced each drive using the GUI and then used the commands above. My drives are connected to SATA ports inside.