YES, but not automatically. Changing the minimum participation size in the DAOS tab of the server doc will affect the storage LOCATION of any attachments WRITTEN from that POINT forward. If you run a copy-style compact (compact -c somefile.nsf) on an NSF that is already participating in DAOS, attachments that are in DAOS but no longer meet the minimum participation size will be stored inline in the resulting NSF. The reference COUNT for the NLO file will be decremented to reflect this. If the resulting reference count reaches zero, the NLO file becomes a candidate for deletion. 

Yes, but not automatically. Changing the minimum participation size in the DAOS tab of the server doc will affect the storage location of any attachments written from that point forward. If you run a copy-style compact (compact -c somefile.nsf) on an NSF that is already participating in DAOS, attachments that are in DAOS but no longer meet the minimum participation size will be stored inline in the resulting NSF. The reference count for the NLO file will be decremented to reflect this. If the resulting reference count reaches zero, the NLO file becomes a candidate for deletion.