Path: csiph.com!usenet.pasdenom.info!news.redatomik.org!newsfeed.xs4all.nl!newsfeed8.news.xs4all.nl!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.010 X-Spam-Evidence: '*H*': 0.98; '*S*': 0.00; 'anyway.': 0.04; 'true,': 0.04; 'subject:Python': 0.05; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'underlying': 0.09; 'corrupt': 0.16; 'received:80.91.229.3': 0.16; 'received:plane.gmane.org': 0.16; 'wrote:': 0.16; 'runs': 0.18; 'machine': 0.21; 'suppose': 0.22; 'header:In-Reply-To:1': 0.24; 'header:User-Agent:1': 0.26; 'header:X-Complaints-To:1': 0.26; 'finds': 0.29; 'hash': 0.29; 'periodic': 0.29; 'monitored': 0.33; 'received:comcast.net': 0.33; 'another': 0.34; 'file': 0.34; 'server': 0.34; 'to:addr:python- list': 0.35; 'newer': 0.35; 'but': 0.36; 'being': 0.36; 'client': 0.37; 'subject:: ': 0.37; 'received:org': 0.38; 'pm,': 0.39; 'does': 0.39; 'to:addr:python.org': 0.39; 'secure': 0.61; 'charset:windows-1252': 0.65; 'results': 0.66; 'subject:Data': 0.66; 'situation': 0.67; 'integrity': 0.76; 'smith': 0.76; 'presumably': 0.84; 'checks.': 0.91 X-Injected-Via-Gmane: http://gmane.org/ To: python-list@python.org From: Randall Smith Subject: Re: Pure Python Data Mangling or Encrypting Date: Tue, 30 Jun 2015 12:43:11 -0500 References: <558b7e85$0$1648$c3e8da3$5496439d@news.astraweb.com> <558bc912$0$2899$c3e8da3$76491128@news.astraweb.com> <558c1a7e$0$1668$c3e8da3$5496439d@news.astraweb.com> <558d86b0$0$1659$c3e8da3$5496439d@news.astraweb.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Gmane-NNTP-Posting-Host: c-98-251-140-107.hsd1.ms.comcast.net User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 In-Reply-To: X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.20+ 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: 19 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1435686305 news.xs4all.nl 2837 [2001:888:2000:d::a6]:37059 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:93344 On 06/29/2015 03:49 PM, Jon Ribbens wrote: > On 2015-06-29, Randall Smith wrote: >> Same reason newer filesystems like BTRFS use checkusms (BTRFS uses >> CRC32). The storage machine runs periodic file integrity checks. It >> has no control over the underlying filesystem. > > True, but presumably neither does it have anything it can do to > rectify the situation if it finds a problem, and the client will > have to keep its own secure hash of its file anyway. (Unless I suppose > the server actually can request a new copy from the client or another > server if it finds a corrupt file?) > Yes. The storage servers are monitored for integrity. They can request a new copy, though frequent corruption results in the server being marked as unreliable. -Randall