Hi,
I have a new server getting delivered in the next few days with some 3TB Seagate drives. I am planning a raidz3 with this, which would get expanded with more raidz3 vdev's later. Once I follow the gnop option to create the initial raidz3 with an ashift of 12, is there a way to make sure that all future raidz3's also get an ashift of 12 automatically? Or is the ashift set for the whole pool? I checked the zdb config from one of my otherfreebsd FreeBSD zfs boxes with 5 raidz2's and it shows an ashift of 9 for each vdev. Using gnop and exporting and reimporting the pool is ok initially with no data in the pool, but I wouldn't want that with a nearly full and heavily used pool and at the time of expansion. So is there a way to avoid this procedure for later raidz3 vdev additions and make that ashift of 12 persistent for the whole pool?
One other question is when a drive fails and it gets replaced, is there anything special that needs to be done to add to the pool with an ashift of 12? (like using gnop again for the replacement drive?) It looks like it would be a while before 4k only drives come out. If it ends up being way too much trouble, I may not fiddle around with ashift, as the 512B emulation may not be going away soon. I can always create a new pool with 4k only drives later in the worst case instead of adding to the current pool.
Thanks.
I have a new server getting delivered in the next few days with some 3TB Seagate drives. I am planning a raidz3 with this, which would get expanded with more raidz3 vdev's later. Once I follow the gnop option to create the initial raidz3 with an ashift of 12, is there a way to make sure that all future raidz3's also get an ashift of 12 automatically? Or is the ashift set for the whole pool? I checked the zdb config from one of my other
One other question is when a drive fails and it gets replaced, is there anything special that needs to be done to add to the pool with an ashift of 12? (like using gnop again for the replacement drive?) It looks like it would be a while before 4k only drives come out. If it ends up being way too much trouble, I may not fiddle around with ashift, as the 512B emulation may not be going away soon. I can always create a new pool with 4k only drives later in the worst case instead of adding to the current pool.
Thanks.