All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@linuxhacker.ru>
To: Andrew Morton <akpm@osdl.org>
Cc: Nick Piggin <piggin@cyberone.com.au>,
	axboe@suse.de, linux-kernel@vger.kernel.org
Subject: Re: Badness in as_completed_request at drivers/block/as-iosched.c:919
Date: Thu, 23 Oct 2003 09:37:42 +0300	[thread overview]
Message-ID: <20031023063742.GA2011@linuxhacker.ru> (raw)
In-Reply-To: <20031022132755.7bfae6a0.akpm@osdl.org>

Hello!

On Wed, Oct 22, 2003 at 01:27:55PM -0700, Andrew Morton wrote:
> > The warning should be harmless. I'll remove it once I make sure. I
> > don't think there have been any recent as-iosched changes, so something
> > else must have just triggered it off.
> The smartd failure doesn't look harmless:
> Device: /dev/sdb, SMART Failure: DATA CHANNEL IMPENDING FAILURE DATA ERROR RATE TOO HIGH
> Or does this always happen?

Yes, drive thinks it is. I am aware of this. But kernel looks surprised.
I have another scsi drive in that system whose smart status is OK, and kernel
does not produce this sort of output when smartd is adding /dev/sda to monitor
list.

> I assume we're dealing with a non-fs request here.

I think you are right, though I think filesystems from that drive might be
already mounted by the time smartd is started.

Bye,
    Oleg

      parent reply	other threads:[~2003-10-23  6:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-22 12:32 Badness in as_completed_request at drivers/block/as-iosched.c:919 Oleg Drokin
2003-10-22 12:51 ` Nick Piggin
2003-10-22 20:27   ` Andrew Morton
2003-10-23  2:21     ` Nick Piggin
2003-10-23  6:37     ` Oleg Drokin [this message]

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=20031023063742.GA2011@linuxhacker.ru \
    --to=green@linuxhacker.ru \
    --cc=akpm@osdl.org \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=piggin@cyberone.com.au \
    /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.