Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #26361

Re: CRC-checksum failed in gzip

Date 2012-08-01 16:17 +0200
From Laszlo Nagy <gandalf@shopzeus.com>
Subject Re: CRC-checksum failed in gzip
References <CAF_E5JahAZ4w3em_aqBbx63pxiTU-nqtRLZWb5_jRQr2yqhRWA@mail.gmail.com> <50190ED6.1040100@shopzeus.com> <CAF_E5JbQHe-iDr=32HX4cxTVHSR2JL=UB3EWjZyVRC_JubUkJw@mail.gmail.com> <50192EBE.3060404@shopzeus.com> <CAF_E5JbkGk8=-k+KCRYOO3EYZWgAkJ8XxH7CmnTmJ5waN36Z_A@mail.gmail.com>
Newsgroups comp.lang.python
Message-ID <mailman.2829.1343830652.4697.python-list@python.org> (permalink)

Show all headers | View raw


>
> Thanks a lotl, someone that writes on the file while reading might be
> an explanation, the problem is that everyone claims that they are only
> reading the file.
If that is true, then make that file system read only. Soon it will turn 
out who is writing them. ;-)
>
> Apparently this file is generated once and a long time after only read
> by two different tools (in sequence), so this could not be possible
> either in theory.. I'll try to investigate more in this sense since
> it's the only reasonable explation I've found so far.
>
Safe solution would be to develop a system where files go through 
"states" in a predefined order:

* allow programs to write into files with .incomplete extension.
* allow them to rename the file to .complete.
* create a single program that renames .complete files to .gz files 
AFTER making them read-only for everybody else.
* readers should only read .gz file
* .gz files are then guaranteed to be complete.

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread


Thread

Re: CRC-checksum failed in gzip Laszlo Nagy <gandalf@shopzeus.com> - 2012-08-01 16:17 +0200

csiph-web