[gpfsug-discuss] mmapplypolicy didn't migrate everything it should have - why not?

Yaron Daniel YARD at il.ibm.com
Wed Apr 19 17:23:12 BST 2017


Hi

Maybe the temp list file - fill the FS that they build on.

Try to monitor the FS where the temp filelist is created.

 
Regards
 


 
 
Yaron Daniel
 94 Em Ha'Moshavot Rd

Server, Storage and Data Services - Team Leader  
 Petach Tiqva, 49527
Global Technology Services
 Israel
Phone:
+972-3-916-5672
 
 
Fax:
+972-3-916-5672
 
 
Mobile:
+972-52-8395593
 
 
e-mail:
yard at il.ibm.com
 
 
IBM Israel
 
 
 
 

 



From:   Bryan Banister <bbanister at jumptrading.com>
To:     gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Date:   04/19/2017 07:19 PM
Subject:        Re: [gpfsug-discuss] mmapplypolicy didn't migrate 
everything it should    have - why not?
Sent by:        gpfsug-discuss-bounces at spectrumscale.org



Hey Marc,
 
I?m having some issues where a simple ILM list policy never completes, but 
I have yet to open a PMR or enable additional logging.  But I was 
wondering if there are known reasons that this would not complete, such as 
when there is a symbolic link that creates a loop within the directory 
structure or something simple like that.
 
Do you know of any cases like this, Marc, that I should try to find in my 
file systems?
 
Thanks in advance!
-Bryan
 
From: gpfsug-discuss-bounces at spectrumscale.org [
mailto:gpfsug-discuss-bounces at spectrumscale.org] On Behalf Of Marc A 
Kaplan
Sent: Wednesday, April 19, 2017 9:37 AM
To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Subject: Re: [gpfsug-discuss] mmapplypolicy didn't migrate everything it 
should have - why not?
 
Well  I'm glad we followed Mr. S. Holmes dictum which I'll paraphrase... 
eliminate the impossible and what remains, even if it seems improbable, 
must hold.

BTW - you may want to look at  mmclone.  Personally, I find the doc and 
terminology confusing, but mmclone was designed to efficiently store 
copies and near-copies of large (virtual machine) images.  Uses 
copy-on-write strategy, similar to GPFS snapshots, but at a file by file 
granularity.

BBTW - we fixed directories - they can now be huge (up to about 2^30 
files) and automagically, efficiently grow and shrink in size.  Also small 
directories can be stored efficiently in the inode.  The last major 
improvement was just a few years ago.  Before that they could be huge, but 
would never shrink. 



Note: This email is for the confidential use of the named addressee(s) 
only and may contain proprietary, confidential or privileged information. 
If you are not the intended recipient, you are hereby notified that any 
review, dissemination or copying of this email is strictly prohibited, and 
to please notify the sender immediately and destroy this email and any 
attachments. Email transmission cannot be guaranteed to be secure or 
error-free. The Company, therefore, does not make any guarantees as to the 
completeness or accuracy of this email or any attachments. This email is 
for informational purposes only and does not constitute a recommendation, 
offer, request or solicitation of any kind to buy, sell, subscribe, redeem 
or perform any type of transaction of a financial product.
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20170419/0f7ff5c9/attachment-0002.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1851 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20170419/0f7ff5c9/attachment-0002.gif>


More information about the gpfsug-discuss mailing list