On Fri, Nov 29, 2013 at 8:35 PM, Jeff Hammond <[email protected]> wrote:

Personally, I'd address the paranoia by saving a copy of your files into a read-only directory. Since I know where you're running, I can say that we should be able to afford the extra storage. If not, let me know and I'll address it. And note also that NERSC $SCRATCH is not backed up, so the safe place to story anything valuable is $HOME. I'm not sure about project directories but I imagine there are docs on this.

It would be nice if it were possible to do read-only MPI-IO in a read-only directory. I don't have a clue what the technical challenges are. Can you not make just the files read-only but let new files be created in the directory?

It's not an issue for me personally anymore: chmod +w . is fine, and symlinks would also solve the problem. The question was more about the motivation for the code and whether it's an issue anything thinks is worth fixing (or fixable at all). That and Jed asked me several times to start the thread. :) Geoffrey