persistent NFS export mount points when changing pool sources

[donish]

Hello,

I am trying to use TrueNAS to serve home directories via NFS on a pool of 4TB drives:

Code:

$showmount -e truenas
Export list for truenas:
/mnt/wd4tb/home/dave       (everyone)

If I migrate the home directories to a new, larger pool of 8tb drives, I must modify the fstab on each client to reflect this because the export has changed:

Code:

$showmount -e truenas
Export list for truenas:
/mnt/wd8tb/home/dave       (everyone)

I would like this to be streamlined such that there are no fstab changes on the clients (they shouldn't care that I'm migrating pools).

I've considered and rejected the following solutions:

1. Use mount_nullfs to bind the nfs export to a persistent path. [mount --bind in linux, used often there]
   1. this doesn't seem to work nicely in truenas, as nfs detects crossmount and prevents it.
2. Change the mount point of the home data set to a pool-independent path
   1. this gets away from the spirit of truenas and is poo-pooed by the community
3. Use client scripts to mount the home directory based on the export list
   1. this solution is easy enough, but really is it necessary for something so simple?

What am I missing? This should be easy?