Re: How to safely maintain a status file

From	Christian Heimes <lists@cheimes.de>
Subject	Re: How to safely maintain a status file
Date	2012-07-14 14:38 +0200
References	(2 earlier) <4FF9F454.40207@shopzeus.com> <jtcvf8$ock$1@dough.gmane.org> <4FFEC371.5040703@shopzeus.com> <mailman.2038.1342098831.4697.python-list@python.org> <4fff7f4c$0$29965$c3e8da3$5496439d@news.astraweb.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.2113.1342269522.4697.python-list@python.org> (permalink)

Show all headers | View raw

Am 13.07.2012 03:52, schrieb Steven D'Aprano:
> And some storage devices (e.g. hard drives, USB sticks) don't actually 
> write data permanently even when you sync the device. They just write to 
> a temporary cache, then report that they are done (liar liar pants on 
> fire). Only when the cache is full, or at some random time at the 
> device's choosing, do they actually write data to the physical media. 
> 
> The result of this is that even when the device tells you that the data 
> is synched, it may not be.

Yes, that's another issue. Either you have to buy expensive enterprise
hardware with UPS batteries or you need to compensate for failures on
software level (e.g. Hadoop cluster).

We have big storage devices with double redundant controllers, on board
buffer batteries, triple redundant power supplies, special RAID disks,
multipath IO fiber channel links and external backup solution to keep
our data reasonable safe.

Christian

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

Thread

Re: How to safely maintain a status file Christian Heimes <lists@cheimes.de> - 2012-07-12 15:05 +0200
  Re: How to safely maintain a status file Ross Ridge <rridge@csclub.uwaterloo.ca> - 2012-07-12 11:48 -0400
  Re: How to safely maintain a status file Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-07-13 01:52 +0000
    Re: How to safely maintain a status file Christian Heimes <lists@cheimes.de> - 2012-07-14 14:38 +0200

csiph-web