linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jim Klimov <klimov@2ka.mipt.ru>
To: linux-raid@vger.kernel.org
Subject: Re[2]: Concept problem with RAID1?
Date: Fri, 24 Mar 2006 19:15:20 +0300	[thread overview]
Message-ID: <392345161.20060324191520@2ka.mipt.ru> (raw)

Hello PFC,

Friday, March 24, 2006, 7:07:04 PM, you wrote:

P>      I think you would like something like this :

P>      A LVM (or dm- device mapper) layer which sits between the RAID layer and
P> the physical disks. This layer computes checksums as data is written to
P> the physical disks, and checks read data against these checksums.

P>      Problem is, where do you store the checksums ?
Why not store the checksums on the same device that stores the
blocks? For example, let a 64-kb (65536b) block of data store,
say, 65520 bytes of data and 16 bytes of checksum/digest and a
timestamp. If the hardware goes crazy and some bits (or more)
are mixed up, we can detect if the data is not trustworthy -
the checksum and/or data is screwed and they don't match each
other. A drawback is the impossibility to mount such a device
as-is, and some loss of performance in addressing/buffering
which I think is okay as a tradeoff for reliability.

A good thing (arguably) would be a capability of raid1 layer
to interact with this checksummed layer during rebuilds or even
casual work. If a block is found to be bad on one submirror,
it could be read (and re-written) from another, valid, copy
without remaking the whole metadevice.

-- 
Best regards,
 Jim Klimov                            mailto:klimov@2ka.mipt.ru


             reply	other threads:[~2006-03-24 16:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-24 16:15 Jim Klimov [this message]
2006-03-24 16:39 ` Re[2]: Concept problem with RAID1? John Rowe

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=392345161.20060324191520@2ka.mipt.ru \
    --to=klimov@2ka.mipt.ru \
    --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).