Sorry for any confusion. MIGRATing a file does NOT change the replication factor, unless you explicitly use the keyword REPLICATE.
The default replication factor, as set/displayed by mm[ch|ls]fs -r only applies at file creation time, unless overriden by a policy SET POOL ... REPLICATE(x) rule. From: Stephen Ulmer <[email protected]> To: gpfsug main discussion list <[email protected]> Date: 06/23/2017 01:55 PM Subject: Re: [gpfsug-discuss] Replication settings when running mmapplypolicy Sent by: [email protected] On Jun 23, 2017, at 12:58 PM, Marc A Kaplan <[email protected]> wrote: I believe that is correct. If not, let us know! To recap... when running mmapplypolicy with rules like: ... MIGRATE ... REPLICATE(x) ... will change the replication factor to x, for each file selected by this rule and chosen for execution. ... MIGRATE ... /* no REPLICATE keyword */ will not mess with the replication factor I think I detect an impedance mismatch... By "not mess with the replication factor" do you mean that after the move: the file will have the default replication factor for the file system the file will retain a replication factor previously set on the file You told Kevin that he was correct and I think he meant the first one, but I read what you said as the second one. Liberty, -- Stephen _______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
_______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
