I had this exact problem (on 9.2, 9.2.1.3, and 9.2.1.5), and solved it by increasing the size of my system pool.
I had this problem every time I tried to install a second plugin (any plugin; the first always installed fine, and the second always threw this error).
My system partition (small, only 3GB) wasn't displaying a disk-space alert most of the times the error occured, but I'd imagine this is because even at 60% used, the space needed to create a a second plugin's jail/other items was more than was available.
Rather than growing the pool (which would work as well), I just destroyed the volume on which my system pool lived (it was dedicated; no other storage used that volume), added a disk, and re-created it. After re-pointing the system pool to that device (via the option in System -> Settings -> Advanced), I was able to install as many plugins as I needed.
On FreeNAS setups where the system pool is on another volume that holds other data, make sure there are at least a few GB free on that volume if you're trying to install plugins. If not, plugin installation may succeed after freeing up space (plugins take up more space than you'd think they would, which I think is because their jails are provisioned for extra space so that plugin-internal databases and the like have room to grow).
I highly recommend creating a dedicated volume for your system pool. This gives you assurance that the only space-related conflicts that occur on it are due to other system-level things; not just ordinary user data filling up the volume.
This may not be the only/single cause of the mapping error, but it certainly resolved the issue for me.
It would also be nice if FreeNAS changed the error message in a future release to be something more informative than "format requires a mapping", e.g. "could not create space for plugin jail on volume ____".
Tl;dr: plugins take up space on your system pool, and trying to install them without sufficient space is one of the causes of the "format requires a mapping" error.