Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!feeder2.ecngs.de!ecngs!feeder.ecngs.de!xlned.com!feeder1.xlned.com!newsfeed.xs4all.nl!newsfeed6.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.026 X-Spam-Evidence: '*H*': 0.95; '*S*': 0.00; 'true,': 0.04; 'predefined': 0.07; 'read-only': 0.07; 'rename': 0.07; 'extension.': 0.09; 'cc:addr:python-list': 0.10; ';-)': 0.11; 'investigate': 0.16; 'renames': 0.16; 'subject:failed': 0.16; '(in': 0.18; 'file.': 0.20; 'cc:2**0': 0.23; "i've": 0.23; 'cc:no real name:2**0': 0.24; 'cc:addr:python.org': 0.25; 'header:In- Reply-To:1': 0.25; 'header:User-Agent:1': 0.26; 'far.': 0.29; 'writes': 0.30; 'sense': 0.31; 'file': 0.32; 'could': 0.32; 'problem': 0.33; 'everyone': 0.33; 'thanks': 0.34; "i'll": 0.36; 'should': 0.36; 'turn': 0.36; 'possible': 0.37; 'two': 0.37; 'subject:: ': 0.38; 'files': 0.38; 'received:192': 0.39; 'where': 0.40; 'received:192.168': 0.40; 'subject:-': 0.40; 'safe': 0.63; 'different': 0.63; 'more': 0.63; 'making': 0.64; 'else.': 0.65; 'readers': 0.65; 'everybody': 0.69; 'soon': 0.70; 'received:204': 0.72; 'guaranteed': 0.76; 'order:': 0.84 Date: Wed, 01 Aug 2012 16:17:25 +0200 From: Laszlo Nagy User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0 MIME-Version: 1.0 To: andrea crotti Subject: Re: CRC-checksum failed in gzip References: <50190ED6.1040100@shopzeus.com> <50192EBE.3060404@shopzeus.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: python-list@python.org X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 24 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1343830652 news.xs4all.nl 6892 [2001:888:2000:d::a6]:43688 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:26361 > > 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.