Re: [gpfsug-discuss] AFM weirdness

2017-08-25 Thread Simon Thompson (IT Research Support)
trumscale.org<mailto:gpfsug-discuss@spectrumscale.org>> Date: Wednesday, 23 August 2017 at 14:01 To: "gpfsug-discuss@spectrumscale.org<mailto:gpfsug-discuss@spectrumscale.org>" <gpfsug-discuss@spectrumscale.org<mailto:gpfsug-discuss@spectrumscale.org>> Subj

Re: [gpfsug-discuss] AFM weirdness

2017-08-23 Thread Simon Thompson (IT Research Support)
ss@spectrumscale.org>>, Simon Thompson <s.j.thomp...@bham.ac.uk<mailto:s.j.thomp...@bham.ac.uk>> Subject: Re: [gpfsug-discuss] AFM weirdness I believe this error is result of preallocation failure, but traces are needed to confirm this. AFM caching modes does not support preallocatio

Re: [gpfsug-discuss] AFM weirdness

2017-08-23 Thread Simon Thompson (IT Research Support)
OK so I checked and if I run directly on the "AFM" FS in a different "non AFM" directory, it works fine, so its something AFM related ... Simon On 23/08/2017, 11:11, "gpfsug-discuss-boun...@spectrumscale.org on behalf of Simon Thompson (IT Research Support)"

[gpfsug-discuss] AFM weirdness

2017-08-23 Thread Simon Thompson (IT Research Support)
We're using an AFM cache from our HPC nodes to access data in another GPFS cluster, mostly this seems to be working fine, but we've just come across an interesting problem with a user using gfortran from the GCC 5.2.0 toolset. When linking their code, they get a "no space left on device" error