Restore does not create zvols with correct metadata

[sukerman]

Hi All,

Sorry I wasn't sure if this was a bug or where to report it so I'll just ask.

I've got a container :

NAME                       PROPERTY      VALUE         SOURCE
bigpool/subvol-100-disk-2  compression   on            inherited from bigpool
bigpool/subvol-100-disk-2  recordsize    16K           local
bigpool/subvol-100-disk-2  atime         off           local
bigpool/subvol-100-disk-2  primarycache  metadata      local

But when I restore it :

NAME                        PROPERTY      VALUE         SOURCE
pool-hdd/subvol-101-disk-2  compression   on            inherited from pool-hdd
pool-hdd/subvol-101-disk-2  recordsize    128K          default
pool-hdd/subvol-101-disk-2  atime         on            default
pool-hdd/subvol-101-disk-2  primarycache  all           default

Is this a bug or expected behaviour? Its a big restore so it hasn't completed yet and I don't know if it would have updated at the end of the restore but this is surely too late as it would have written the data at the wrong recordsize?

Thanks,

Jack.

 

[Alwin]

Is this a bug or expected behaviour? Its a big restore so it hasn't completed yet and I don't know if it would have updated at the end of the restore but this is surely too late as it would have written the data at the wrong recordsize?

The backup of a container is file based, it will not save the recordsize.

bigpool/subvol-100-disk-2 recordsize 16K local

The recordsize has been set by hand locally to the subvol.