From: Jens Axboe <axboe@suse.de>
To: Satish Kumar <m_satish@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bdev manipulation at block layer level
Date: Wed, 25 Jul 2001 11:50:55 +0200 [thread overview]
Message-ID: <20010725115055.D834@suse.de> (raw)
In-Reply-To: <20010725091716.71588.qmail@web11502.mail.yahoo.com>
In-Reply-To: <20010725091716.71588.qmail@web11502.mail.yahoo.com>
On Wed, Jul 25 2001, Satish Kumar wrote:
> Hi,
>
> I have a host PC connected to a disk array with
> alternate paths to an end scsi disk.
> I attempted load balancing across paths by changing
> the b_dev & b_rdev ib the bufer_head list in
> ll_rw_block function of ll_rw_blk.c (block layer), and
> was successful in load balancing with data integrity,
> on linux 2.2.16.
> However, when I try the same stunt with a linux 2.4 (
> &2.4.2) kernel, I am seeing corruption occasionally.
> Can anyone let me know if I am missing anything ?
You must not change b_dev, that will screw the cache! Just change b_rdev
to redirect the I/O and it should work.
--
Jens Axboe
prev parent reply other threads:[~2001-07-25 10:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-25 9:17 bdev manipulation at block layer level Satish Kumar
2001-07-25 9:50 ` Jens Axboe [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=20010725115055.D834@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=m_satish@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox