[GRASS-dev] r.in.gdal and xargs

[Blumentrath, Stefan]

Hi again,

Now, I investigated a bit more:

When I use just one process in xargs (P 1) I get no error.  r.mapcalc works nicely together with the same xargs approach and 10 processes.
I think this can be tracked down to the creation of the directory .tmp/HOST which seems to fail if more processes try to create it at (almost) the same time...

The temp-file creation behavior seems affects also other modules like e.g. r.null.

Opened a ticket on trac:
https://trac.osgeo.org/grass/ticket/3309

Cheers
Stefan


-----Original Message-----
From: grass-dev [mailto:grass-dev-bounces at lists.osgeo.org] On Behalf Of Blumentrath, Stefan
Sent: mandag 6. mars 2017 15.57
To: Vincent Bain <bain at toraval.fr>
Cc: GRASS developers list (grass-dev at lists.osgeo.org) <grass-dev at lists.osgeo.org>
Subject: Re: [GRASS-dev] r.in.gdal and xargs

I can parallelize on a higher level, so i can set P to 1 here.
If it is a bug I can open a ticket... 

________________________________________
Von: Vincent Bain [bain at toraval.fr]
Gesendet: Montag, 6. März 2017 15:07
An: Blumentrath, Stefan
Cc: GRASS developers list (grass-dev at lists.osgeo.org)
Betreff: Re: [GRASS-dev] r.in.gdal and xargs

Yes, perhaps something to do with r.in.gdal temp files handling.

And what if you try to reduce P value ?
well, of course it will slow down the bulk import...


Le lundi 06 mars 2017 à 14:02 +0000, Blumentrath, Stefan a écrit :
> Thanks Vincent for your swift reply.
>
> In principle the pipe to xargs works, as 99% of the data is imported properly. And also in the case were I get roors, the command is started properly...
>
> Thus, I suspect that r.in.gdal can have issues when run in parallel; or the creation of temp files, in particular the creation of the .tmp/HOST directory within the mapset...
>
> Cheers
> Stefan
>
>


_______________________________________________
grass-dev mailing list
grass-dev at lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev