All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: erich <erich@areca.com.tw>
Cc: dax@gurulabs.com,
	"\"(????????????)??????O\"" <billion.wu@areca.com.tw>,
	Al Viro <viro@ftp.linux.org.uk>, Andrew Morton <akpm@osdl.org>,
	"Randy.Dunlap" <rdunlap@xenotime.net>,
	Matti Aarnio <matti.aarnio@zmailer.org>,
	linux-kernel@vger.kernel.org,
	James Bottomley <James.Bottomley@steeleye.com>,
	Chris Caputo <ccaputo@alt.net>
Subject: Re: new Areca driver in 2.6.16-rc6-mm2 appears to be broken
Date: Wed, 19 Apr 2006 12:40:09 +0200	[thread overview]
Message-ID: <20060419104009.GB614@suse.de> (raw)
In-Reply-To: <002901c65e33$ceac9e00$b100a8c0@erich2003>

On Wed, Apr 12 2006, erich wrote:
> Dear Jens Axboe,
> 
> I had found a big difference of generic_make_request(struct bio *bio)
> got message : sdb1: rw=0, want=...., limit=.....
> 
> 
> *****************
> ** TEST 1
> *****************
> 
> I used "MAX_XFER_SECTORS  4096" driver to do mkfs.ext2 with ARECA RAID 
> volume sdb1.
> and copy a big file (900MB) into sdb1.
> If I copy this file from sdb1, the message rw=.... ,want=......, 
> limit=...... will appear immediately.
> 
> When I reboot the system and used  "MAX_XFER_SECTORS  512" driver.
> I copy this big file from sdb1, the message rw=.... ,want=......, 
> limit=...... still appear immediately.

This to me looks like you have a corrupted fs after using the 4k sectors
as the max transfer setting. I would look for a bug in the driver that
could explain this. Or perhaps the hardware.

Can you try and boot with MAX_XFER_SECTORS at 4096 and run mkfs + copy
big file to the partition. umount, then boot a kernel with
MAX_XFER_SECTORS at 512 and do a full fsck of that partition.


-- 
Jens Axboe


  reply	other threads:[~2006-04-19 10:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.64.0603212310070.20655@nacho.alt.net>
2006-03-30  8:54 ` new Areca driver in 2.6.16-rc6-mm2 appears to be broken erich
2006-03-30 15:46   ` Chris Caputo
     [not found]     ` <004a01c65470$412daaa0$b100a8c0@erich2003>
     [not found]       ` <20060330192057.4bd8c568.akpm@osdl.org>
     [not found]         ` <20060331074237.GH14022@suse.de>
2006-03-31  8:36           ` erich
2006-04-12 13:20           ` erich
2006-04-19 10:40             ` Jens Axboe [this message]
2006-04-19 13:16               ` erich
2006-04-19 13:19                 ` Jens Axboe
2006-04-20  1:54                   ` erich
2006-04-20  6:42                     ` Jens Axboe
2006-04-20  8:11                       ` erich
2006-04-20  8:23                         ` Jens Axboe
2006-04-20  9:32                           ` erich
2006-04-20  9:39                             ` Jens Axboe
2006-04-20 12:53                           ` James Bottomley
2006-04-20 15:38                         ` Randy.Dunlap
2006-04-25  8:45                           ` erich
2006-04-25 16:02                             ` Randy.Dunlap
2006-04-26  3:24                               ` erich

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=20060419104009.GB614@suse.de \
    --to=axboe@suse.de \
    --cc=James.Bottomley@steeleye.com \
    --cc=akpm@osdl.org \
    --cc=billion.wu@areca.com.tw \
    --cc=ccaputo@alt.net \
    --cc=dax@gurulabs.com \
    --cc=erich@areca.com.tw \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matti.aarnio@zmailer.org \
    --cc=rdunlap@xenotime.net \
    --cc=viro@ftp.linux.org.uk \
    /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.