A few years ago I had to replace 3 disks in a raidz with larger disks. At the time I had to use some trickery that involved a sparse file that pretended to be the same size as one of my disks - I can't quite remember the process now and I can no longer find the article/blog post I read at the time.
Anyway, I'm needing to do this again and I've noticed there is now a 'autoexpand' attribute that can be set on a pool. Am I correct in thinking that if I set this to on, I can simply replace a disk at a time and let them resilver despite the fact that the disks are larger in size?
OK so I kind of answered part of my own question. The following should work.
However I don't have a free slot to put the new disk in and run 'zpool replace'. So will I be able to replace a disk if it is removed? I will test this in a virtual environment anyway but curious to hear if others have any experience.
Anyway, I'm needing to do this again and I've noticed there is now a 'autoexpand' attribute that can be set on a pool. Am I correct in thinking that if I set this to on, I can simply replace a disk at a time and let them resilver despite the fact that the disks are larger in size?
OK so I kind of answered part of my own question. The following should work.
Code:
# zpool create pool c0t0d0
# zpool list
NAME SIZE ALLOC FREE CAP HEALTH ALTROOT
pool 8.44G 76.5K 8.44G 0% ONLINE -
# zpool replace pool c0t0d0 c1t13d0
# zpool list
NAME SIZE ALLOC FREE CAP HEALTH ALTROOT
pool 8.44G 91.5K 8.44G 0% ONLINE -
# zpool set autoexpand=on pool
# zpool list
NAME SIZE ALLOC FREE CAP HEALTH ALTROOT
pool 16.8G 91.5K 16.8G 0% ONLINE -
However I don't have a free slot to put the new disk in and run 'zpool replace'. So will I be able to replace a disk if it is removed? I will test this in a virtual environment anyway but curious to hear if others have any experience.