All of lore.kernel.org
 help / color / mirror / Atom feed
From: ashwin chaugule <ashwin.chaugule@gmail.com>
To: Greg Freemyer <greg.freemyer@gmail.com>,
	LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Re: raid 1 on a single disk
Date: Sun, 14 Nov 2004 11:14:20 +0530	[thread overview]
Message-ID: <89af10f904111321441f2a3a1e@mail.gmail.com> (raw)
In-Reply-To: <87f94c37041113140053f493b0@mail.gmail.com>

There Greg ! , you got it right !
The media onto which the data will be stored is a small device, that
functions like a hdd,
this endeavour was just for a proof of concept.

I've also managed to hack into the kernel IDE susbsys. (ide-disk.c) to
duplicate the writes and reads for this particular disk.

So now I have two options for them.

RAID 1 is useful here (although its on one disk) because , data will
not be written / read _very_ often to/from the device. And in the
event that the media is flaky, will provide like a backup. The other
benefit is, I dont have to worry about the i/o errors (or any other
for that matter) while reading the contents back, the best copy
*should* be picked up by the md subsys itself.

However, in my driver (modified IDE) I have to take care of the writes
and reads individualy.
The advantage here is that, i dont need to make 4 partitions of the
disk, one is good enough, and the remaining can be unallocated. I make
the write at fixed offsets into the unallocated space, and when read
is requested, I read em one by one, and check.

So, there.


On Sat, 13 Nov 2004 17:00:35 -0500, Greg Freemyer
<greg.freemyer@gmail.com> wrote:
> >
> > P.S. I'd be really tempted to talk to the person asking you to do this, and ask them what they hope to achieve...
> > 
> I can almost envision times it would be useful.  i.e. disk speed is
> unimportand, disk data rarely changes, but when it does it is very
> important, and traditional backups are not feasible for some unknown
> reason?
> 
> By having the data written to 2 different places on the disk, the
> likelyhood of a failure making it  truly unrecoverable is extremely
> small.
> 
> ie. If you have disk media problems, likely only one location of the
> other will be affected.
> 
> If you have a drive electronics failure, you can ship the drive off to
> have recovery performed.  (Over $1000 I know, but if the data is
> important.)
> 
> Greg
> 
> _______________________________________________
> 
> 
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
> 


-- 
Ashwin Chaugule
Embedded Systems Engineer
Aftek Infosys ltd.
[Embedded Division]

  parent reply	other threads:[~2004-11-14  5:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-13 10:17 [linux-lvm] raid 1 on a single disk ashwin chaugule
2004-11-13 10:33 ` [linux-lvm] " Peter T. Breuer
2004-11-13 10:41   ` ashwin chaugule
2004-11-13 11:03     ` Piete Brooks
2004-11-13 12:59     ` Peter T. Breuer
2004-11-13 13:38       ` Piete Brooks
2004-11-13 15:04         ` Peter T. Breuer
2004-11-13 13:38       ` ashwin chaugule
2004-11-13 21:13     ` Graham Wood
2004-11-13 22:00       ` Greg Freemyer
2004-11-14  0:41         ` Måns Rullgård
2004-11-14  5:44         ` ashwin chaugule [this message]
2004-11-14 11:28           ` Peter T. Breuer
2004-11-14 17:41             ` ashwin chaugule
2004-11-14 18:04               ` Peter T. Breuer
2004-11-14 19:02                 ` ashwin chaugule
2004-11-14 21:01                   ` Peter T. Breuer
2004-11-15  6:09                     ` ashwin chaugule

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=89af10f904111321441f2a3a1e@mail.gmail.com \
    --to=ashwin.chaugule@gmail.com \
    --cc=greg.freemyer@gmail.com \
    --cc=linux-lvm@redhat.com \
    /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.