linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
To: David Brown <david.brown@hesbynett.no>
Cc: Linux Raid <linux-raid@vger.kernel.org>,
	Bernd Schubert <bernd.schubert@fastmail.fm>
Subject: Re: Checksumming RAID?
Date: Tue, 27 Nov 2012 12:39:34 +0100 (CET)	[thread overview]
Message-ID: <22100889.14.1354016374529.JavaMail.root@zimbra> (raw)
In-Reply-To: <50B4A215.4000203@hesbynett.no>

> I can certainly sympathise with you, but I am not sure that data
> checksumming would help here. If your hardware raid sends out
> nonsense,
> then it is going to be very difficult to get anything trustworthy. The
> obvious answer here is to throw out the broken hardware raid and use a
> system that works - but it is equally obvious that that is easier said
> than done! But I would find it hard to believe that this is a common
> issue with hardware raid systems - it goes against the whole point of
> data storage.
> 
> There is always a chance of undetected read errors - the question is
> if
> the chances of such read errors, and the consequences of them, justify
> the costs of extra checking. And if they /do/ justify extra checking,
> are data checksums the right way?

The chance of a silent corruption is rather small with your average 3TB home storage. On the other hand, if you had a petabyte or five, the chances would be very high indeed to get silent corruption (ref the CERN study done in 2007). In my last job, I worked with ZFS with ~350TiB storage, and there we saw errors happen rather frequently, but then, since ZFS checksums data and uses it to deal with errors, we never saw any data loss. That is, except on an older machine, running ZFS on a hardware RAID controlled storage unit (NexSAN SATABeast). We had error corruption on that one as well, after a disk failure, and had to resort to restoring from tape, since ZFS couldn't control the RAID.

> I agree with Neil's post that
> end-to-end checksums (such as CRCs in a gzip file, or GPG integrity
> checks) are the best check when they are possible, but they are not
> always possible because they are not transparent.

The problem with end-to-end-checksums at the application level, is it will only be able to detect the error, not fix it, similar to the issues I mentioned above.

Vennlige hilsener / Best regards

roy
--
Roy Sigurd Karlsbakk
(+47) 98013356
roy@karlsbakk.net
http://blogg.karlsbakk.net/
GPG Public key: http://karlsbakk.net/roysigurdkarlsbakk.pubkey.txt
--
I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det er et elementært imperativ for alle pedagoger å unngå eksessiv anvendelse av idiomer med xenotyp etymologi. I de fleste tilfeller eksisterer adekvate og relevante synonymer på norsk.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-11-27 11:39 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-26 13:27 Checksumming RAID? Roy Sigurd Karlsbakk
2012-11-27  9:45 ` David Brown
2012-11-27 10:17   ` Bernd Schubert
2012-11-27 11:20     ` David Brown
2012-11-27 11:39       ` Roy Sigurd Karlsbakk [this message]
2012-11-27 12:37         ` David Brown
2012-11-27 13:09           ` Roy Sigurd Karlsbakk
2012-11-27 13:20             ` David Brown
2012-11-27 13:56               ` Roy Sigurd Karlsbakk
2012-11-27 14:34                 ` David Brown
2012-11-27 20:49           ` Stan Hoeppner
2012-11-28 10:58             ` Roy Sigurd Karlsbakk
2012-11-27 12:31       ` Bernd Schubert
2012-11-27 13:05         ` David Brown
2012-11-27 18:53           ` Chris Murphy
2012-11-27 19:27             ` Roy Sigurd Karlsbakk
2012-11-27 19:50               ` Chris Murphy
2012-11-28 10:56                 ` Roy Sigurd Karlsbakk
2012-11-28 10:59                   ` Roy Sigurd Karlsbakk
2012-11-28 13:25                   ` Drew
2012-11-28 17:51                     ` Roy Sigurd Karlsbakk
2012-11-28 19:16                       ` Chris Murphy
2012-11-28 19:08                   ` Chris Murphy
2012-11-28 19:18                     ` Roy Sigurd Karlsbakk
2012-11-28 20:02                       ` Chris Murphy
2012-11-27 13:54       ` Joe Landman
2012-11-27 18:48   ` Chris Murphy
2012-11-27 19:36     ` Chris Murphy
2012-12-03 12:24 ` Pasi Kärkkäinen
2012-12-03 14:09   ` Checksumming RAID? / SCSI SAS T10 PI and DIF/DIX / T13 SATA EPP Pasi Kärkkäinen
2012-12-05 19:05     ` Martin K. Petersen
2012-12-06 11:10       ` John Robinson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=22100889.14.1354016374529.JavaMail.root@zimbra \
    --to=roy@karlsbakk.net \
    --cc=bernd.schubert@fastmail.fm \
    --cc=david.brown@hesbynett.no \
    --cc=linux-raid@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).