linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 107371] New: I/O error when accessing disk in standby
Date: Fri, 06 Nov 2015 11:42:54 +0000	[thread overview]
Message-ID: <bug-107371-11613@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=107371

            Bug ID: 107371
           Summary: I/O error when accessing disk in standby
           Product: SCSI Drivers
           Version: 2.5
    Kernel Version: 4.1.2
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Other
          Assignee: scsi_drivers-other@kernel-bugs.osdl.org
          Reporter: nikmind@home.se
        Regression: No

I got a LSI 2308 SAS controller (using the mpt2sas driver) and are noticing odd
I/O errors on my disk.

Example:

[398374.597662] sd 0:0:4:0: [sde] UNKNOWN(0x2003) Result: hostbyte=0x00
driverbyte=0x00
[398374.597665] sd 0:0:4:0: [sde] CDB: opcode=0x88 88 00 00 00 00 00 c0 52 c3
90 00 00 00 08 00 00
[398374.597667] blk_update_request: I/O error, dev sde, sector 3226649488

It happenes to all disks on the controller. I can't seem to notice any problems
due to this, but something does not seem right about getting this error. I also
checked the offending sectors and it's no problem reading them.

So i started to investigate this problem and soon found that the problem occurs
when the disk is in standby mode. Ie. when I try to access the disk when it is
in standby mode. Somehow the system tries to access the disk without spinning
it up first, and hence getting this error. I also checked the offending sectors
and there is no problem reading them.

I don't notice any problems due to this error, but I don't think this error
should occur.

It's very easy to replicate.

1. run "hdparm -y" on the disk to spin it down.
2. Access the disk in any way, like list a directory.
3. Getting this I/O error above, but this getting the dirlist as if nothing
wen't wrong.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2015-11-06 11:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-06 11:42 bugzilla-daemon [this message]
2015-11-06 11:53 ` [Bug 107371] I/O error when accessing disk in standby bugzilla-daemon
2015-11-06 13:15 ` bugzilla-daemon
2020-08-27 22:08 ` bugzilla-daemon

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=bug-107371-11613@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).