From: "Raphaël Bauduin" <rblists@gmail.com>
To: linux-scsi@vger.kernel.org
Subject: strange observation, the queue depth is (64) meanwhile fw queue depth (65)
Date: Thu, 27 Mar 2014 15:21:29 +0100 [thread overview]
Message-ID: <lh1c4r$uss$1@ger.gmane.org> (raw)
Hi,
I have these messages logged on 2 different servers (one production, one
stand-by) when using recent vanilla kernels.
I have found references to these logs, but this was supposedly
introduced in the 2.6.31 kernel.
However, running kernel 2.6.32.61, this message does not appear. It
appears when running kernel versions 3.12.15, 3.13.1 and 3.13.6. I
haven't tested other intermediate kernel versions.
We had once the root filesystem remounted read-only on the production
server, and we found no significant error messages other than the one in
the subject of this mail. This makes me wary to ignore these messages,
and since then we went back to kernel 2.6.32.61.... I've tried running
kernels mentioned above on the stand-by server, and get the errors there
too.
Here is the exact error message from dmesg:
[ 3776.788033] sd 7:1:0:0: strange observation, the queue depth is (64)
meanwhile fw queue depth (65)
and below are some other extracts from dmesg.
Both servers have these errors on a RAID1 volume on which the root
partition is located.
I hope someone can help me to resolve this. I can send any information
you might require.
Thanks in advance
Raphaël
[ 2.978053] SCSI subsystem initialized
[ 2.979969] Fusion MPT base driver 3.04.20
[ 2.980059] Copyright (c) 1999-2008 LSI Corporation
[ 3.712015] ioc0: LSISAS1064E B3: Capabilities={Initiator}
[ 16.516096] scsi7 : ioc0: LSISAS1064E B3, FwRev=01182b00h, Ports=1,
MaxQ=286, IRQ=16
[ 16.536672] mptsas: ioc0: attaching ssp device: fw_channel 0, fw_id
2, phy 0, sas_addr 0x500000e01ee1a602
[ 16.538312] scsi 7:0:0:0: Direct-Access FUJITSU MBC2073RC
5201 PQ: 0 ANSI: 5
[ 16.542605] mptsas: ioc0: attaching ssp device: fw_channel 0, fw_id
1, phy 1, sas_addr 0x500000e01edab602
[ 16.544158] scsi 7:0:1:0: Direct-Access FUJITSU MBC2073RC
5201 PQ: 0 ANSI: 5
[ 16.548445] mptsas: ioc0: attaching raid volume, channel 1, id 0
[ 16.549304] scsi 7:1:0:0: Direct-Access LSILOGIC Logical Volume
3000 PQ: 0 ANSI: 2
[ 16.556492] sd 7:1:0:0: [sdr] 140623872 512-byte logical blocks:
(71.9 GB/67.0 GiB)
[ 16.556824] sd 7:1:0:0: [sdr] Write Protect is off
[ 16.556895] sd 7:1:0:0: [sdr] Mode Sense: 03 00 00 08
[ 16.557109] sd 7:1:0:0: [sdr] No Caching mode page found
[ 16.557180] sd 7:1:0:0: [sdr] Assuming drive cache: write through
[ 16.558258] sd 7:1:0:0: [sdr] No Caching mode page found
[ 16.558329] sd 7:1:0:0: [sdr] Assuming drive cache: write through
[ 16.575039] sdr: sdr1 sdr2
[ 16.576018] sd 7:1:0:0: [sdr] No Caching mode page found
[ 16.576088] sd 7:1:0:0: [sdr] Assuming drive cache: write through
[ 16.576356] sd 7:1:0:0: [sdr] Attached SCSI disk
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2014-03-27 14:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 14:21 Raphaël Bauduin [this message]
2014-03-28 13:18 ` strange observation, the queue depth is (64) meanwhile fw queue depth (65) Raphaël Bauduin
2014-04-08 7:13 ` Raphaël Bauduin
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='lh1c4r$uss$1@ger.gmane.org' \
--to=rblists@gmail.com \
--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.