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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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" <[email protected]>
To: "erich" <[email protected]>
Cc: <[email protected]>; ""(????????????)??????O"" <[email protected]>; "Al Viro" <[email protected]>; "Andrew Morton" <[email protected]>; "Randy.Dunlap" <[email protected]>; "Matti Aarnio" <[email protected]>; <[email protected]>; "James Bottomley" <[email protected]>; "Chris Caputo" <[email protected]>
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


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux