Bug 171159 - ll_rw_block: device 08:XX: only 4096-char blocks implemented (1024)
Summary: ll_rw_block: device 08:XX: only 4096-char blocks implemented (1024)
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: kernel   
(Show other bugs)
Version: 2.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Brian Brock
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-10-18 20:20 UTC by Anu Matthew
Modified: 2007-11-30 22:06 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-10-18 22:08:49 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Anu Matthew 2005-10-18 20:20:26 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7

Description of problem:
Problem evident on RHEL AS 2.1 running kernel-2.4.9-e.65 or kernel-smp-2.4.9-e.62 with QLogic Corp. QLA2312 Fibre Channel Adapter (rev 02) cards. 

Say, there are 4 LUNs from Symmetrix, and /dev/sdb and /dev/sdc are alt devices

[root@plrac01 root]# scsi_info /dev/sdb 
SCSI_ID="0,0,6"
MODEL="EMC SYMMETRIX"
FW_REV="5568"

[root@plrac01 root]# scsi_info /dev/sdc 
SCSI_ID="0,0,7"
MODEL="EMC SYMMETRIX"
FW_REV="5568"


Cleared the ring buffer using dmesg -c, 

[root@plrac01 root]# dmesg
[root@plrac01 root]# dmesg

Querying the devices using fdisk -l, logs "ll_rw_block: device 08:XY: only 4096-char blocks implemented (1024)" , where XY varies on the drive you queried.

For example,. 
[root@plrac01 root]# fdisk -l /dev/sdb 

Disk /dev/sdb: 255 heads, 63 sectors, 9903 cylinders
Units = cylinders of 16065 * 512 bytes

Disk /dev/sdb doesn't contain a valid partition table
[root@plrac01 root]# dmesg
ll_rw_block: device 08:10: only 4096-char blocks implemented (1024)
ll_rw_block: device 08:10: only 4096-char blocks implemented (1024)

Now, query the other device:

[root@plrac01 root]# fdisk -l /dev/sdc 

Disk /dev/sdc: 255 heads, 63 sectors, 9903 cylinders
Units = cylinders of 16065 * 512 bytes

Disk /dev/sdc doesn't contain a valid partition table
[root@plrac01 root]# dmesg
ll_rw_block: device 08:10: only 4096-char blocks implemented (1024)
ll_rw_block: device 08:10: only 4096-char blocks implemented (1024)
ll_rw_block: device 08:20: only 4096-char blocks implemented (1024)
ll_rw_block: device 08:20: only 4096-char blocks implemented (1024)


This is evident only in systems running with qla2300 modules loaded. No such messages are logged on RHEL AS 2.1 systems runnign lpfc/lpfcdd at same kernel levels. 

Here are the details of the cards 

lspci o/p: 
06:01.0 Fibre Channel: QLogic Corp. QLA2312 Fibre Channel Adapter (rev 02)
06:02.0 Fibre Channel: QLogic Corp. QLA2312 Fibre Channel Adapter (rev 02)

Info from /proc/scsi/qla2300/

<snip>
QLogic PCI to Fibre Channel Host Adapter for QLA2340         :
        Firmware version:  3.03.01, Driver version 7.01.01-RH1
Entry address = f8826060
HBA: QLA2312 , Serial# L53796
<snip>








Version-Release number of selected component (if applicable):
kernel-smp-2.4.9-e.62, kernel-2.4.9-e.65, 

How reproducible:
Always

Steps to Reproduce:
1.RHEL AS 2.1 with above mentioned kernel levels.
2.Above mentioned Qlogic cards
3.Try querying your SAN devices using "fdisk -l", this message will appear. 
  

Actual Results:  Logs like

ll_rw_block: device 08:10: only 4096-char blocks implemented (1024)
ll_rw_block: device 08:20: only 4096-char blocks implemented (1024)

Expected Results:  It should not log any message. 

Additional info:

This is evident on rhel as 2.1 and Qlogic cards mentioned above. This problem is not observed on lpfc/lpfcdd modules.

Comment 1 Don Howard 2005-10-18 22:08:49 UTC
Hi Anu -

Have you had a chance to open a ticket with RH support for this issue?
(https://www.redhat.com/apps/support/)   That's the best channel for enterprise
linux bug reports.




Note You need to log in before you can comment on or make changes to this bug.