[GRASS-dev] [GRASS GIS] #2764: corrupt data written to FCELL and DCELL rasters, hard to re-produce
GRASS GIS
trac at osgeo.org
Sun Jan 7 12:25:07 PST 2018
#2764: corrupt data written to FCELL and DCELL rasters, hard to re-produce
---------------------+-------------------------
Reporter: dylan | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.2.3
Component: Raster | Version: unspecified
Resolution: | Keywords:
CPU: x86-64 | Platform: Linux
---------------------+-------------------------
Comment (by mmetz):
Replying to [comment:21 dylan]:
> Replying to [comment:20 mmetz]:
>
> > > Could there be a lurking zlib compression bug in the code that only
manifests during parallel invocation, or, when a very large number of rows
are involved?
> >
> > I don't think so because
> > 1. you can't reproduce the error with a SSD
> > 2. Markus N can't reproduce the error with a SSD
> > 3. I can't reproduce the error with a SSD or an old spinning HDD (no
RAID) or a NAS with spinning disks and software RAID 5
> >
> > Therefore I guess that something is wrong with your hard drive or
there is a bug in your filesystem driver or there is a bug in your RAID
management/configuration (in case you are still using a software RAID 1
system).
>
> All good points, except that this iteration of errors (grass-user
messages and tickets filed since 2017-12-30) have all been encountered
while working on an ssd exclusively. Unless of course temp files are
stored outside of the database/mapset. I'll work on a short list of all
related tickets and mailing list posts.
If you are not using the test scripts attached to this ticket any more,
can you please also add data and commands that trigger this error to this
ticket? Thanks!
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2764#comment:22>
GRASS GIS <https://grass.osgeo.org>
More information about the grass-dev
mailing list