lkml.org 
[lkml]   [2005]   [Jun]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Linux does not care for data integrity
Helge Hafting wrote:

> Bill Davidsen wrote:
>
>> Matthias Andree wrote:
>>
>>> On Sun, 29 May 2005, Greg Stark wrote:
>>>
>>>
>>>> Oracle, Sybase, Postgres, other databases have hard requirements. They
>>>> guarantee that when they acknowledge a transaction commit the data
>>>> has been
>>>> written to non-volatile media and will be recoverable even in the
>>>> face of a
>>>> routine power loss.
>>>>
>>>> They meet this requirement just fine on SCSI drives (where write
>>>> caching
>>>> generally ships disabled) and on any OS where fsync issues a cache
>>>> flush. If
>>>
>>>
>>>
>>>
>>> I don't know what facts "generally ships disabled" is based on, all of
>>> the more recent SCSI drives (non SCA type though) I acquired came with
>>> write cache enabled and some also with queue algorithm modifier set
>>> to 1.
>>>
>>>
>>>> Worse, if the disk flushes the data to disk out of order it's quite
>>>> likely the entire database will be corrupted on any simple power
>>>> outage. I'm not clear whether that's the case for any common drives.
>>>
>>>
>>>
>>>
>>> It's a matter of enforcing write order. In how far such ordering
>>> constraints are propagated by file systems, VFS layer, down to the
>>> hardware, is the grand question.
>>>
>> The problem is that in many options required to make that happen in
>> the o/s, hardware, and application are going to kill performance. And
>> even if you can control order of write, unless you can get write to
>> final non-volatile media control you can get a sane database but
>> still lose transactions.
>>
>> If there was a way for the o/s to know when a physical write was done
>> other than using flushes to force completion, then overall
>> performance could be higher, but individual transaction might have
>> greater latency. And the app could use fsync to force order of write
>> as needed. In many cases groups of writes can be done in any order as
>> long as they are all done before the next logical step takes place.
>
>
> There is a workaround. Get an UPS just for the disks. It don't have
> to be
> big, just enough to keep the disks going long enough to commit their
> caches after the rest of the machine died from a power loss. Such a
> small
> unit could possibly fit inside the cabinet, avoiding the trouble with
> people stepping on the power cord.
>
> With this in place, any write that makes it from the controller to the
> disk is safely stored for all practical purposes.


Unfortunately even drives in a dual power tray with redundany power from
separate UPS sources will occasionally have a power failure. Proved that
last month, the power strip in the rack failed, dumped all the load on
the other leg, the surge tripped a breaker. Had an APC UPS in my office
fail in a mode which dropped power, waited for the battery to trickle
charge to charge the battery a bit, then repeat. Looks to be losing half
of a full wave rectifier.

The point is that power failures WILL HAPPEN, even with good backups.
The goal should be to prevent excessive and avoidable data damage when
it does.

Shameless plug: for office use I changed from APC to Belkin on all new
units, they have had Linux drivers for some time now, and I like to
support those who support Linux.

--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-06-02 14:04    [W:0.437 / U:1.312 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site