Level2 - Couldn't open the directory: Input/output error about force

[davidfrantz]

Hi @kesslerf,

I have no idea to be honest. This is very unusual and such things are typically rather related to the system or hardware.
It might be that discs that are too slow, that the network is shortly interrupted, or probably a slow file system is used.. Really hard to say....

I also have no experience with running FORCE through Docker from Python, but I don't think that this is causing these issues.

The only thing in the parameterfile that was striking, is that you overtask the VM. 4 Processes with 4 threads equals 16 CPUs (8 are available). However, I don't believe that this is causing write/read errors.

Sorry for not giving you a more specific answer.
David

[kesslerf]

Thanks for the reply, I actually expected this to be kind of unfamiliar. As it is not my own filesystem it might be due to errors on the servers etc..

Thanks for the hint about the parameters, i will change the param-files to address this. Which of the two variables should I set to 2 instead of 4?

Thanks,
Felix

[davidfrantz]

Using more processes than threads will be more efficient:

NPROC = 4
NTHREAD = 2

You could even try

NPROC = 8
NTHREAD = 1

With 64GB RAM, this might work.

Is this a cloud? Do you use block or object storage? Object storage might not work very well with the writing patterns of FORCE.

Cheers,
David

[kesslerf]

Thank you. I am using force in a docker-swarm and some machines have different setup due to limitations in total amount of RAM etc.

I will probably go for 8 and 1 and see if there is a huge difference in processing time.

We are using a cloud yes, but I am in no way an expert in anything of these so I can not answer the question, sorry.