Is fs_dedupe turned on on the source, or are there any tree quotas?
do an fs_dedupe -l on the source VNX. That could potentially affect how big the filesystem is on the target, assuming automatic creation.
Perhaps its due to an underlying block size difference with UFS64 compared to UXFS. That's just a guess of course, I'm sure someone with more insight here probably already knows the definitive answer.
crklosterman
450 Posts
694
1
Posted November 1st, 2017 09:00
Is fs_dedupe turned on on the source, or are there any tree quotas?
do an fs_dedupe -l on the source VNX. That could potentially affect how big the filesystem is on the target, assuming automatic creation.
Perhaps its due to an underlying block size difference with UFS64 compared to UXFS. That's just a guess of course, I'm sure someone with more insight here probably already knows the definitive answer.
~Chris