linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chuck Ebbert <76306.1226@compuserve.com>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid <linux-raid@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] raid1: allow user to force reads from a specific disk
Date: Mon, 7 Aug 2006 04:45:50 -0400	[thread overview]
Message-ID: <200608070447_MC3-1-C756-23FA@compuserve.com> (raw)

In-Reply-To: <17622.35724.43741.529875@cse.unsw.edu.au>

On Mon, 7 Aug 2006 10:38:36 +1000, Neil Brown wrote:

> > Allow user to force raid1 to read all data from a given disk.
> > This lets users do integrity checking by comparing results
> > from reading different disks.  If at any time the system finds
> > it cannot read from the given disk it resets the disk number
> > to -1, the default, which means to balance reads.
> 
> Could say a little bit more about why you want this?
> 
> You could get nearly the same situation be setting the other drives to
> write-mostly. 

But you couldn't test whether all IO had really gone to the target disk
after doing some reads.

e.g.

        echo 0 >/sys/block/md0/md/read_from_disk
        mount -t ext3 /dev/md0 /mnt/md0
        find /mnt/md0 -type f | xargs md5sum
        cat /sys/block/md0/md/read_from_disk

If the output from the last command isn't 0 then not all reads came from
that disk.

> And the more thorough integrity check is available via
>    echo check > /sys/block/mdX/md/sync_action

I tried that.  It doesn't do anything but print the raid status to the
kernel log.  Either that or on my 100MB mirror it's able to thoroughly
check the integrity in less than 1/4 second.

-- 
Chuck

             reply	other threads:[~2006-08-07  8:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-07  8:45 Chuck Ebbert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-07  0:15 [patch] raid1: allow user to force reads from a specific disk Chuck Ebbert
2006-08-07  0:38 ` Neil Brown
2006-08-17 15:04 ` Pavel Machek

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=200608070447_MC3-1-C756-23FA@compuserve.com \
    --to=76306.1226@compuserve.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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).