All of lore.kernel.org
 help / color / mirror / Atom feed
From: PFC <lists@peufeu.com>
To: Jim Klimov <klimov@2ka.mipt.ru>, linux-raid@vger.kernel.org
Subject: Re: Concept problem with RAID1?
Date: Fri, 24 Mar 2006 17:07:04 +0100	[thread overview]
Message-ID: <op.s6xdp2nmcigqcu@apollo13> (raw)
In-Reply-To: <212703968.20060324131659@2ka.mipt.ru>



	I think you would like something like this :

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

	Problem is, where do you store the checksums ? You need a rather fast,  
non-volatile memory to do this. An interesting option would be an USB key.  
However, flash memory has a limited number of write cycles. Some scheme  
would be needed to not always overwrite the same spot on the flash memory.

	Interesting...

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

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

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=op.s6xdp2nmcigqcu@apollo13 \
    --to=lists@peufeu.com \
    --cc=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 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.