Re: new Areca driver in 2.6.16-rc6-mm2 appears to be broken

erich
2006-04-19T13:16:34Z

Dear Jens Axboe,

About your request :

******************************************
** boot with driver MAX_XFER_SECTORS 4096
******************************************
#mkfs.ext2 /dev/sda1
#mount /dev/sda1 /mnt/sda1
#cp /root/aa /mnt/sda1/
#reboot
******************************************
** boot with driver MAX_XFER_SECTORS 512
******************************************
#fsck /dev/sda1
/dev/sda1:clean,.............
#mount /dev/sda1 /mnt/sda1
#cp /mnt/sda1/aa /home
cp: reading '/mnt/sda1/aa' : input/output error
got message : sda1: rw=0, want=...., limit=..... dump

Best Regards
Erich Chen

----- Original Message -----
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>
Sent: Wednesday, April 19, 2006 6:40 PM
Subject: Re: new Areca driver in 2.6.16-rc6-mm2 appears to be broken

> 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
>