From: Jeff Johnson <jeff.johnson@aeoncomputing.com>
To: linux-raid@vger.kernel.org
Subject: Re: OT: silent data corruption reading from hard drives
Date: Thu, 02 Aug 2012 10:13:55 -0700 [thread overview]
Message-ID: <501AB553.2030003@aeoncomputing.com> (raw)
In-Reply-To: <CABYL=TpDU0YD4orJqyZzeYPtUJ+vBEeM=CWhFxa4GWGj8SjGMQ@mail.gmail.com>
The only ways I know of to currently detect/repair silent data
corruption are via the use of T10-DIF on SAS drives with 520-byte
sectors and embedded per block CRCs (bytes 513-520) or via a patented
algorithm used in a commercial Linux software RAID product
(www.streamscale.com).
Neither approach is cost effective for small or personal use RAID
applications.
On 8/2/12 10:04 AM, Roberto Spadim wrote:
> well i think the integrity is know, but it´s not fully needed since
> the security isn´t a problem we can buy secure sata/sas
> controlers/disks
> the main problem will be in some days when we are using SoC systems
> and we only have USB to connect a harddrive... maybe when this become
> more popular we will see a development of a module to have data
> integrity (silient corruption detection and maybe repair)
>
--
------------------------------
Jeff Johnson
Manager
Aeon Computing
jeff.johnson@aeoncomputing.com
www.aeoncomputing.com
t: 858-412-3810 x101 f: 858-412-3845
m: 619-204-9061
/* New Address */
4170 Morena Boulevard, Suite D - San Diego, CA 92117
--
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
next prev parent reply other threads:[~2012-08-02 17:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 12:02 OT: silent data corruption reading from hard drives matt
2012-08-01 13:03 ` Roman Mamedov
2012-08-02 0:56 ` Stan Hoeppner
2012-08-02 1:07 ` Roberto Spadim
2012-08-02 1:14 ` Roberto Spadim
2012-08-02 1:27 ` Adam Goryachev
2012-08-02 1:35 ` Roberto Spadim
2012-08-02 3:23 ` Stan Hoeppner
2012-08-02 13:02 ` Drew
2012-08-02 3:19 ` Roman Mamedov
2012-08-02 7:51 ` Stan Hoeppner
2012-08-02 8:06 ` Roman Mamedov
2012-08-02 9:29 ` Stan Hoeppner
2012-08-02 12:26 ` Iustin Pop
2012-08-02 16:59 ` listy
2012-08-02 17:04 ` Roberto Spadim
2012-08-02 17:13 ` Jeff Johnson [this message]
2012-08-02 17:19 ` Roman Mamedov
2012-08-02 17:25 ` Roberto Spadim
2012-08-02 17:22 ` Roberto Spadim
[not found] ` <501AB9D8.1030404@turmel.org>
2012-08-02 18:32 ` listy
2012-08-03 13:36 ` Phil Turmel
2012-08-15 21:55 ` Peter Grandi
2012-08-16 7:30 ` Oliver Schinagl
[not found] ` <CABYL=TqU6qvDK-CuFak42iVNj0v4OcvALXOnr=6XLM4HyXfGkw@mail.gmail.com>
2012-08-16 14:33 ` Roberto Spadim
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=501AB553.2030003@aeoncomputing.com \
--to=jeff.johnson@aeoncomputing.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.