Thanks for the update.
What you describe is not what I am experiencing.
I have
sancontrol-01 etc]# grep vol0 exports
/vol/vol0 -sec=sys,rw=192.168.252.10:192.168.145.255:sancontrol-01.example.ca,anon=0,nosuid
sancontrol-01 etc]# cat hosts.equiv
#Auto-generated by setup Sat Dec 19 00:30:03 GMT 2009
sancontrol-01
When any volume was created including clones we would see a corresponding export
/vol/vol_23042015_085125 -sec=sys,rw,nosuid
and a clone of the same volume.
/vol/vol_23042015_085125_clone_23042015_085227 -sec=sys,rw,nosuid
Note that /vol0 isn't on the same aggregate as the new volume
sangw1> vol status vol_23042015_085125
Volume State Status Options
vol_23042015_085125 online raid0, flex create_ucode=on, convert_ucode=on,
64-bit guarantee=none, fractional_reserve=0
Volume has clones: vol_23042015_085125_clone_23042015_085227
Volume UUID: 9ef2ca3d-e9d0-11e4-bf57-123478563412
Containing aggregate: 'aggr3_sata'
sangw1> vol status vol_23042015_085125_clone_23042015_085227
Volume State Status Options
vol_23042015_085125_clone_23042015_085227 online raid0, flex create_ucode=on, convert_ucode=on,
64-bit guarantee=none, fractional_reserve=0
Clone, backed by volume 'vol_23042015_085125', snapshot 'clone_vol_23042015_085.1'
Volume UUID: c1a68f55-e9d0-11e4-bf57-123478563412
Containing aggregate: 'aggr3_sata'