Would anyone find the following options to the 'move data' command
useful?

type
   all - all data on volume, default
   backup - backup data
   archive - archive data
   spacemanaged - space managed data
   - allow pairs of the above three types

node
   - specify a list of nodes whose data is to be moved

filespace
   - specify a list of filespaces whose data is to be moved - may
require
   the node option specified

Since migration from sequential storage pools to sequential storage
pools
already moves collocation clusters, the implementation of the latter two

options should be trivial.  The implementation of the first option might
be
more difficult but would be immensely valuable.  I've seen a number of
situations where backup, archive, and space managed data are mixed in
a storage pool (bad idea from a data integrity point of view) and there
is
currently no way to separate the data.

Anyone agree on this?

Cheers...
Bruce