https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-7996 Lustre <p>I added about 30 TB of space to our nearly full Lustre file system. Now, the original OSTs are almost full with only about 500GB left. How can I even out the space between them and the new OSTs? I was reading on lfs_migrate bit I am unsure of the syntax and if I should run it on the OSS? Thanks.</p> RHEL 5.9 LU-7996

Load Balance After Adding New OST's

Question/Request Minor Resolved Done WC Triage Frank Thu, 7 Apr 2016 21:28:01 +0000 Mon, 11 Apr 2016 17:57:28 +0000 Mon, 11 Apr 2016 17:57:28 +0000 Lustre 1.8.9 0 2 <p>There is a man page for <tt>lfs_migrate</tt> even in 1.8.9. Note, however, that migration on Lustre 1.8.x is not safe against use/modification by other processes/clients that are using a file during migration. You will somehow have to "know" that files are idle based on how your workload and environment are configured, or which users/applications are currently active. The main concern is if files are being modified during migration and the new data is discarded (despite checks to try and avoid this), or if processes have the old version of the file open and do not see new data being written to the file after it is migrated.If your applications don't modify files after they have been written then this is not a concern. </p> <p>In order to reduce this risk, you can selectively migrate only older files, for example only large files changed more than 7 days ago:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>lfs find /testfs -size +4G -ctime +7d | lfs_migrate </pre> </div></div> <p>With Lustre 2.5.x and later, it is possible to safely migrate files while they might be open and in use.</p> Development Rank 1|hzy793: Rank (Obsolete) 9223372036854775807