All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Vasquez <andrew.vasquez@qlogic.com>
To: Csillag Tamas <cstamas@digitus.itk.ppke.hu>
Cc: linux-scsi@vger.kernel.org
Subject: Re: qla2xxx errors? (2.6.19)
Date: Tue, 12 Jun 2007 10:48:54 -0700	[thread overview]
Message-ID: <20070612174854.GD12266@plap.qlogic.org> (raw)
In-Reply-To: <20070610100011.GG5705@digitus>

On Sun, 10 Jun 2007, Csillag Tamas wrote:

> The university I work at has 4 Blade HS20 servers connected to a IBM
> DS400 storage via Fibre Channel.
> The fibre channel module is:
> 
> 06:01.0 Fibre Channel: QLogic Corp. QLA2312 Fibre Channel Adapter (rev 02)
> 06:01.1 Fibre Channel: QLogic Corp. QLA2312 Fibre Channel Adapter (rev 02)
> 
> # lsmod
> Module                  Size  Used by
> ...
> qla2xxx               143584  1
> 
> # l /lib/firmware 
> total 244
> lrwxrwxrwx 1 root root     21 2007-05-05 22:02 ql2300_fw.bin -> ql2300_fw.bin.3.03.18
> 
> With recent kernels filesystem corruption occurs under high disk I/O.
> I have just tried 2.6.19 and I got the same, but kernel 2.6.18 and
> before looks safe.

Could you load the driver with the ql2xextended_error_logging module
parameter enabled:

	$ echo "6 4 1 7"  > /proc/sys/kernel/printk
	$ insmod qla2xxx.ko ql2xextended_error_logging=1

and forward over the resultant messages file beginning with the load
of the driver to the point at which the File-system failure occurs.

> The test I use is the following:
> I first checkout the kernel's git tree:
> # git-clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git linux-2.6.git
> Then
> # for i in {100..400}; do; rsync -a linux-2.6.git/ c2_$i& done
> .... waiting for finish
> # for i in {100..400}; do; rsync -a linux-2.6.git/ c3_$i& done
> .... waiting for finish
> # for i in {100..400}; do; rsync -a linux-2.6.git/ c4_$i& done
> 
> Some error messages:
> ReiserFS: warning: is_tree_node: node level 32010 does not match to the expected one 1
> ReiserFS: sdb1: warning: vs-5150: search_by_key: invalid format found in block 8093723. Fsck?
> ReiserFS: sdb1: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [961831 1064427 0x0 SD]

I can setup somthing similar locally, I take it you are writing
directly some some lun exported off the DS400, and not using DM?

> I am able to reproduce this errors.
> 
> With other filesystems I get similar errors.

Just curious, what are those errors?

> I suspect a bug in qla2xxx, but I am not sure.
> Can you help me how to track down this problem?

Please also provide the output of:

	$ cat /proc/scsi/scsi
	$ lspci -vvx

and your .config file.

Regards,
Andrew Vasquez

  reply	other threads:[~2007-06-12 17:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-10 10:00 qla2xxx errors? (2.6.19) Csillag Tamas
2007-06-12 17:48 ` Andrew Vasquez [this message]
2007-06-12 19:15   ` Csillag Tamas
2007-06-13 20:23   ` Csillag Tamas
2007-06-21 21:41   ` Csillag Tamas
2007-06-26 12:46     ` Andrew Vasquez
2007-06-26 14:31       ` James Bottomley
2007-07-02 23:40         ` Csillag Tamas

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=20070612174854.GD12266@plap.qlogic.org \
    --to=andrew.vasquez@qlogic.com \
    --cc=cstamas@digitus.itk.ppke.hu \
    --cc=linux-scsi@vger.kernel.org \
    /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.