linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Freemyer <greg.freemyer@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Linda Walsh <suse@tlinx.org>, linux-ide@vger.kernel.org
Subject: Re: Port Multiplier access with Sil 3124
Date: Mon, 9 Feb 2009 22:25:19 -0500	[thread overview]
Message-ID: <87f94c370902091925g15bd433dlfe021431acbaaaa8@mail.gmail.com> (raw)
In-Reply-To: <4990C70E.1010707@garzik.org>

On Mon, Feb 9, 2009 at 7:15 PM, Jeff Garzik <jeff@garzik.org> wrote:
> Greg Freemyer wrote:
>
>> I'm hearing of people saying a 2 disk mirror (raid-1) is not safe
>> enough.  Go with either a 3 disk mirror or to raid-6.  Even with
>> raid-6 I personally would not let it have too many spindles. (Whatever
>> too many means?)
>
> IMO, RAID-1 was never safe.  With RAID-1, one must rely solely on "knowing"
> which RAID component is bad.  With a completely dead drive, this is obvious;
> with slowly creeping bad sectors, far less obvious.
>
> Plus, the biggest crime, in my opinion, is the lack of checksumming or any
> other method of actually verifying your data.
>
> I've been waiting for years for someone to write RAID-1f...  RAID-1 with a
> hash function that writes checksums in a special metadata area (just like
> the other pre-existing RAID metadata...  a RAID partition is really a just
> simple filesystem anyway).
>
> That way you _know_ with 100% certainty that your data is OK (or not), even
> if you only have a single drive.
>
>        Jeff

Jeff,

I guess you know the scsi standard is in the process of getting
expanded such that each sector can optionally have a well known hash.
And that the hash can be provided by the kernel as part of the data
write.  In turn it can be read as part of the sector on a data read.

Thus it will be possible to have true end-to-end reliability in a
single disk environment.  Who knows when hardware will start to show
up.  If anyone on this list has any influence on the T13 (ata) spec
people, I think it would be a great addition to the ATA world as well
as for the scsi world.

You can google for "SCSI DIF/DIX extensions"

The linux block layer, dm, and mdraid are all gaining support.  Maybe
you can figure out an efficient way to leverage that infrastructure
and implement raid-1f via libata and normal drives!!!

Greg



-- 
Greg Freemyer
Litigation Triage Solutions Specialist
http://www.linkedin.com/in/gregfreemyer
First 99 Days Litigation White Paper -
http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf

The Norcross Group
The Intersection of Evidence & Technology
http://www.norcrossgroup.com

  parent reply	other threads:[~2009-02-10  3:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-08 20:38 Port Multiplier access with Sil 3124 Linda Walsh
2009-02-09  9:26 ` Grant Grundler
2009-02-09 22:01   ` Linda Walsh
2009-02-09 14:35 ` Greg Freemyer
2009-02-09 20:09   ` Mark Lord
2009-02-09 22:22   ` Linda Walsh
2009-02-09 23:01     ` Greg Freemyer
2009-02-10  0:15       ` Jeff Garzik
2009-02-10  1:07         ` Linda Walsh
2009-02-10  3:48           ` Jeff Garzik
2009-02-11  2:09           ` Tejun Heo
2009-02-12  4:16             ` Robert Hancock
2009-02-10  3:25         ` Greg Freemyer [this message]
2009-02-11  2:12 ` Tejun Heo

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=87f94c370902091925g15bd433dlfe021431acbaaaa8@mail.gmail.com \
    --to=greg.freemyer@gmail.com \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=suse@tlinx.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).