I don't know if this would help you but I use a mod function on the inode of the file to break down the workload into smaller batches across the file system when doing compression and encryption options.
In the policy.. WHERE MOD(INODE,10)<=shares If you ran your encryption as an mmyapplypolicy -M shares=1 sleep 300 mmyapplypolicy -M shares=2 You'd break your work down into 10 steps with 5 minute rests. And the shares would be cumulative so you won't miss any files when you get to 10 it's really doing 1-10.. number of shares can be any arbitrary number. Hope that helps. Alec On Thu, Sep 15, 2022, 9:01 AM Bill Anderson <[email protected]> wrote: > > Hi All, > > We're trying to use both compression and snapshots on our filesystem, > but find that we can't delete snapshots when compression is running. Since > compression can take days or longer to run on our large filesystem (80+ > PB), it's making it impractical to use both on our filesystem. > > Has anyone had experience with using both of these features and have > any tips on their coexistence? > > Thanks! > > Bill > > _______________________________________________ > gpfsug-discuss mailing list > gpfsug-discuss at gpfsug.org > http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org >
_______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at gpfsug.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org
