Re: 3ware 9550SX problems - mke2fs incredibly slow writing last third of inode tables

[adam radford]

On 10/30/05, Alex Bligh - linux-kernel <linux-kernel@xxxxxxxxxxx> wrote:

> All seems to go well until I try and do mke2fs. This appears to work,
> and tries to write the inode tables. However, at (about) 3400 inodes
> (of 11176), it slows to a crawl, writing one table every 10 seconds.
> strace shows it is still running, and no errors are being reported.
> However, it seems very sick.

Do you have cache turned on or off?  If it's off, try turning it on.

>
> No debug messages indicating any errors.
>
> The only other clue as to what may be wrong is in the boot sequence.
> I see lots of bad LUN messages (detail below). However, it does appear
> to be detecting the disks right in the end.
>
> Anyone got any ideas?
>
>
> Oct 30 20:09:09 localhost kernel: [ 138.688249]
> /dev/scsi/host4/bus0/target0/lun0: p1 < p5 >
> Oct 30 20:09:09 localhost kernel: [ 138.712496] Attached scsi disk sdb at
> scsi4, channel 0, id 0, lun 0
> Oct 30 20:09:09 localhost kernel: [ 138.712814] scsi: On host 4 channel 0
> id 0
> only 511 (max_scsi_report_luns) of 214715501 luns reported, try increasing
> max_scsi_report_luns.
> Oct 30 20:09:09 localhost kernel: [ 138.712817] scsi: host 4 channel 0 id 0
> lun 0x383438203636202d has a LUN larger than currently supported.

There were some changes to scsi_scan.c between 2.6.12 and 2.6.14 that
seem to have fixed this issue.  Reproduce with 2.6.14.

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