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, 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: Thu, 20 Apr 2006 10:23:58 +0200	[thread overview]
Message-ID: <20060420082357.GU614@suse.de> (raw)
In-Reply-To: <001e01c66451$f9a470f0$b100a8c0@erich2003>


(don't top post!)

On Thu, Apr 20 2006, erich wrote:
> Dear Dear Jens Axboe,
> 
> Thanks for your notification and advice.
> Areca's firmware has max sg entries of 38 limit.
> In my debug driver I had add this condition check.
> But no one request more than 38 sg.
> Both transfer length all have a lot of requests equal with 38 sg.
> But why it ocur only at 4096 sectors?
> If the /sys/block/sda/queue/max_sectors_kb equal 256 all operation running 
> well.
> But if I modify it more than 256, the bug appeared.
> I  will do more research about why there were a lot of requests equal with 
> 38 sg in all file system.

It was just a suggestion, the bug might very well be just the size of
the transfer itself and nothing SG related. All I can say for sure is
that I'd be very surprised if this fs corruption isn't due to the
hardware mangling the data for large transfers.

> And only it ocur at the volume that format with mkfs.ext2.

Most likely a coincidence, try running eg dbench or other stress tests
on the fs with larger xfer size and I'm sure it'll corrupt eventually as
well.


-- 
Jens Axboe


  reply	other threads:[~2006-04-20  8:23 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
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 [this message]
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=20060420082357.GU614@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.