FreeNAS Code

volume_fstype is spelled as vol_fstype in model.

Fix typo.

Rework r7699. As William pointed out, we use the volume form to add disks
into existing ZFS pool and r7699 prevents this from happening.

Instead of blocking pre-existing volume name, distinguish between ZFS and
UFS and instead block the following situations:

- Creating ZFS when pre-existing non-ZFS file system under the same name
exists;
- Creating UFS when pre-existing any file system exists.

Reviewed by: william

Combine collect restarts down into middleware and make it a hook for after
creation and destroy of a volume or dataset.

Add preliminary code to support resetting freenas:state attribute when deleting
a replication.

Volume name should be unique.

s/occured/occurred/g
s/Some error/An error/g
Replace 'while' with 'when' if appropriate. It sounds much less wordy.

Fix the typos again.. Hopefully these won't get reverted. Blah.

Destroying volumes could leave the database in inconsistent state if there were ZVols currently in use.
Also handle the export of volumes without cascade works as expected

Fix typos.