Bug 81113 - (CCISS)cciss driver giving "check condition, sense key = 0x3" errors
Summary: (CCISS)cciss driver giving "check condition, sense key = 0x3" errors
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 7.3
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-01-04 23:38 UTC by Bill Gunter
Modified: 2007-04-18 16:49 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-09-30 15:40:22 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Bill Gunter 2003-01-04 23:38:30 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1)
Gecko/20020823 Netscape/7.0

Description of problem:
On a Compaq DL380 server with 3x72GB stripe set, ext2 or ext3 or reiserfs
filesystem, rcp of large amounts of data (160GB) produces errors like this in
the syslog.

kernel: cciss: cmd <some hex number> has CHECK CONDITION, sense key = 0x3

Some of the files rcpd over are corrupted, showing different checksums from the
originals while retaining the same size.

I've tried recreating the stripe set several times, and I've replaced all three
disks. The problem seems to happen more frequently with more files being copied
over at the same time.

Running kernel 2.4.18-19.7.xsmp, cciss driver 2.4.30

Version-Release number of selected component (if applicable):


How reproducible:
Sometimes

Steps to Reproduce:
1.rcp of large amounts of data to the filesystem on the cciss array.
2.
3.
    

Additional info:
Comment 1 Bugzilla owner 2004-09-30 15:40:22 UTC 
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/
Note You need to log in before you can comment on or make changes to this bug.