GEOS-ESM/GEOSgcm_App

Move (back) to use cp and tar at NAS

mathomp4 opened this issue · 0 comments

Per Johnny Chang of NASA Ames:

One important caveat is to avoid setting Lustre stripe count and stripe size because this file system uses Progressive File Layout (PFL). In fact, all of our newer Lustre file systems (nobackupp[10-19]) use PFL. Instead of using mcp or shiftc, just use cp or scp to copy or transfer files to /nobackupp18. Both mcp and shiftc will do file striping based on the size of the files -- a feature we don't want when writing to /nobackupp[10-19]. We've asked the mcp/shiftc code developer, Paul Kolano, to turn off file striping for writing into /nobackupp[10-19], but it's going to take a while to change those tools and it may not be worth the effort. For the next several months to 1 year, we'll still have the old Lustre file systems (/nobackupp[1-9]) as well as our newer Lustre file systems while we migrate everyone to the new file systems.

So "soon" we (well, I) should move GEOS to use cp and tar. I moved GEOS to use mcp and mtar because that was the Right Thing™ at NAS, but that is changing soon. (Similar changes will be needed in post.)