Hi, You can stop the AFM resync if it is not required.
mmafmctl device dropPending -j fileset mmafmctl device resetResync -j fileset Next access to the fileset would run the recovery and impact should be minimal as it recovers only the data which was not replicated. ~Venkat ([email protected]) From: Leonardo Sala <[email protected]> To: "[email protected]" <[email protected]> Date: 07/17/2019 07:32 PM Subject: [EXTERNAL] [gpfsug-discuss] Mistakenly AFM resync triggered: should I stop it? Sent by: [email protected] Dear all, I do have a possibly stupid question, based on something stupid I did. During a procedure to recover AFM transfers (which stopped for still to be investigated reasons), I triggered by mistake a resync operation on an healthy SW fileset (state: Inactive). The AFM cache in this case is big, so this has triggered a big backlog and quite some network activity. afmPrefetchThreshold is set to 0, so I am not too scared about partially zero-filled data files. But what would it be the best course of action now? Should I just let it run (ETA: ~20 hours, give or take), or try to stop it? Also, given that this is some experimental data, what would the safest course of action? Thanks a lot! cheers leo -- Paul Scherrer Institut Dr. Leonardo Sala Group Leader High Performance Computing Deputy Section Head Science IT Science IT WHGA/106 5232 Villigen PSI Switzerland Phone: +41 56 310 3369 [email protected] www.psi.ch_______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org https://urldefense.proofpoint.com/v2/url?u=http-3A__gpfsug.org_mailman_listinfo_gpfsug-2Ddiscuss&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=92LOlNh2yLzrrGTDA7HnfF8LFr55zGxghLZtvZcZD7A&m=MapU9QQbtQx-G9hGAGBPzuB-Qxkl0HONn6ByIz4nXoI&s=F_iFVjqia2agf0fTNncWoaZqmKbhSCO-opqFb6cjG6A&e=
_______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
