Hi,
I'm currently having a problem with my zpool. The zpool currently consists of two vdevs, both are raid-z2, both contain four disks. The first vdev contains 4x 1.5 TB and the second 4x 3TB. The server has 4 sata ports and contains an additional sas controller with 8 ports.
Currently I'm facing three problems: the pool is filling up quickly, with only 1TB of storage left, I'm going to be receiving a large backup in a couple weeks of about 700GB, leaving me with around 300GB of spare room. The second problem is that zpool status is complaining that the disks are not using their native block size: "block size: 512B configured, 4096B native".
Lastly, one of the 3TB disks is experiencing intermittent failures. I have to re-add it to the vdev about twice a week and resilver. Obviously the last problem has me worried, but I'm at a loss as to how to go about fixing this.
I would like to upgrade the 1.5TB disks to 4TB disks, in addition I'd like to replace the broken 3TB disk with a 4TB one, so that I can upgrade the other 3 in a while to get a total of 8x 4TB.
In this process I'd like to solve all the above mentioned problems, but as far as I can tell there is no way that you can use different block sizes on different disks in the same vdev, so this means when I replace the broken 3TB disk I'll still be stuck with 512b blocks.
I have the following procedure in mind, but it's cumbersome and feels dangerous:
As far as I can tell this would leave with with one zpool that is correctly configured, and contains all data. But it feels cumbersome and really dangerous. Is there any better way?
I'm currently having a problem with my zpool. The zpool currently consists of two vdevs, both are raid-z2, both contain four disks. The first vdev contains 4x 1.5 TB and the second 4x 3TB. The server has 4 sata ports and contains an additional sas controller with 8 ports.
Currently I'm facing three problems: the pool is filling up quickly, with only 1TB of storage left, I'm going to be receiving a large backup in a couple weeks of about 700GB, leaving me with around 300GB of spare room. The second problem is that zpool status is complaining that the disks are not using their native block size: "block size: 512B configured, 4096B native".
Lastly, one of the 3TB disks is experiencing intermittent failures. I have to re-add it to the vdev about twice a week and resilver. Obviously the last problem has me worried, but I'm at a loss as to how to go about fixing this.
I would like to upgrade the 1.5TB disks to 4TB disks, in addition I'd like to replace the broken 3TB disk with a 4TB one, so that I can upgrade the other 3 in a while to get a total of 8x 4TB.
In this process I'd like to solve all the above mentioned problems, but as far as I can tell there is no way that you can use different block sizes on different disks in the same vdev, so this means when I replace the broken 3TB disk I'll still be stuck with 512b blocks.
I have the following procedure in mind, but it's cumbersome and feels dangerous:
- Remove all 4 1.5TB disks, leaving the entire pool in degraded state.
- Install 4x 4TB disks and create a new zpool using the correct block size.
- Remove two of the new 4TB disks, and install 2x 1.5TB, this should leave both zpools in degraded, but usable state.
- Copy all data to the new pool (this is a problem, because it's going to be slightly too small, although I can shuffle stuff around.)
- Destroy the old zpool, reinstall the last two 4TB disks, resilver. This should put the new zpool into online state, with all data and the correct block size.
- Re-create a vdev with 3x 3TB and 1x 4TB disks, with the correct block size.
As far as I can tell this would leave with with one zpool that is correctly configured, and contains all data. But it feels cumbersome and really dangerous. Is there any better way?