| From: | Alex Ignatov <a(dot)ignatov(at)postgrespro(dot)ru> |
|---|---|
| To: | John R Pierce <pierce(at)hogranch(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Initdb --data-checksums by default |
| Date: | 2016-04-20 08:00:56 |
| Message-ID: | 57173738.3050300@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 20.04.2016 10:47, John R Pierce wrote:
> On 4/20/2016 12:43 AM, Alex Ignatov wrote:
>> Today in Big Data epoch silent data corruption becoming more and more
>> issue to afraid of. With uncorrectable read error rate ~ 10^-15on
>> multiterabyte disk bit rot is the real issue.
>
> are not those uncorrectable errors detected by the disk hardware ?
> thats not 'silent'.
>
> whats the rate of uncorrectable AND undetected read errors ?
>
>
> --
> john r pierce, recycling bits in santa cruz
Uncorrectable read error rate ~ 10^-15- 10^-14. This error stays
undetected and uncorrectable.
Also how can you associate disk block ->> file block without knowing
fs structure? Also not every hardware include this checksum feature
under the hood.
--
Alex Ignatov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Ignatov | 2016-04-20 08:04:52 | Re: Initdb --data-checksums by default |
| Previous Message | Michael Paquier | 2016-04-20 07:58:25 | Re: Initdb --data-checksums by default |