[gpfsug-discuss] mmapplypolicy and ltfsee - identifying progress...

Buterbaugh, Kevin L Kevin.Buterbaugh at Vanderbilt.Edu
Tue Jun 6 22:20:31 BST 2017


Hi Valdis,

I’m not sure this is “better”, but what I typically do is have mmapplypolicy running from a shell script launched by a cron job and redirecting output to a file in /tmp.  Once the mmapplypolicy finishes the SysAdmin’s get the tmp file e-mailed to them and then it gets deleted.  Of course, while the mmapplypolicy is running you can “tail -f /tmp/mmapplypolicy.log” or grep it or whatever.  HTHAL…

Kevin
On Jun 6, 2017, at 3:31 PM, valdis.kletnieks at vt.edu<mailto:valdis.kletnieks at vt.edu> wrote:

So I'm trying to get a handle on where exactly an mmapplypolicy that's
doing a premigrate is in its progress.  I've already determined that
'ltfsee info jobs' will only report where in the current batch it is,
but that still leaves me unable to tell the difference between

[I] 2017-06-05 at 17:31:47.995 Executing file list: /gpfs/archive/config/tmp/
mmPolicy.chosnlist.97168.79FD2A24.pre. 10000 files dispatched.

and

[I] 2017-06-06 at 02:44:48.236 Executing file list: /gpfs/archive/config/tmp/
mmPolicy.chosnlist.97168.79FD2A24.pre. 225000 files dispatched.

Is there any better way to figure out where it is than writing the
cron job to launch it as

mmapplypolicy | tee /tmp/something

and then go scraping the messages? (And yes, I know not all chunks of 1,000
files are created equal.  Sometimes it's 1,000 C source files that total to
less than a megabyte, other times it's 1,000 streaming video files that total
to over a terabye - but even knowing it's 194,000 into 243,348 files is better
than what I have now...)


—
Kevin Buterbaugh - Senior System Administrator
Vanderbilt University - Advanced Computing Center for Research and Education
Kevin.Buterbaugh at vanderbilt.edu<mailto:Kevin.Buterbaugh at vanderbilt.edu> - (615)875-9633



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20170606/368eb1f4/attachment.htm>


More information about the gpfsug-discuss mailing list