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 08:42:50 +0200 [thread overview]
Message-ID: <20060420064249.GO614@suse.de> (raw)
In-Reply-To: <001401c6641d$586bd950$b100a8c0@erich2003>
On Thu, Apr 20 2006, erich wrote:
> Dear Jens Axboe,
>
> I do "fsck -fy /dev/sda1" on driver MAX_XFER_SECTORS 512.
> The file system was not clean.
> I attach mesg.txt for you refer to.
>
> =====================================
> == boot with driver MAX_XFER_SECTORS 4096
> =====================================
> #mkfs.ext2 /dev/sda1
> #reboot
> =====================================
> == boot with driver MAX_XFER_SECTORS 512
> =====================================
> #fsck -fy /dev/sda1
> /dev/sda1:clean,.............
> #reboot
> =====================================
> == boot with driver MAX_XFER_SECTORS 4096
> =====================================
> #mount /dev/sda1 /mnt/sda1
> #cp /root/aa /mnt/sda1
> #reboot
> =====================================
> == boot with driver MAX_XFER_SECTORS 512
> =====================================
> #fsck -fy /dev/sda1
> /dev/sda1: no clean,........and dump message such as the attach file
> mesg.txt.
So the conclusion is that your driver and/or hardware corrupts data when
you set MAX_XFER_SECTORS too high. I can't help you anymore with this,
you should be in the best position to debug the driver and/or hardware
:-)
It could be that the higher setting just exposes another transfer
setting bug, like maximum number of segments or segment size, etc.
--
Jens Axboe
next prev parent reply other threads:[~2006-04-20 6:42 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 [this message]
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=20060420064249.GO614@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox