Hi Jeff & Toasters,
Yup, its the best you can do at this time.
Thanks.
Do you specifically know that this will work as intended though? e.g., as per my original e-mail: "will this actually result in a physical reallocate being performed, or will the deduped blocks still be skipped because they're already de-duplicated, regardless of whether dedupe is enabled for new data on the volume or not?"
I'm re-querying because I struggle to see why de-dupe being on/off for new blocks would affect the ability to reallocate, whereas I can imagine scenarios where blocks /already/ being deduplicated could affect the ability to reallocate.
DO NOT do a reallocate -A.
DO NOT.
Thanks for that Jeff - we'll be very careful to avoid the -A option :-)
Cheers, Matt