From: Andrew Morton <akpm@osdl.org>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: green@linuxhacker.ru, axboe@suse.de, linux-kernel@vger.kernel.org
Subject: Re: Badness in as_completed_request at drivers/block/as-iosched.c:919
Date: Wed, 22 Oct 2003 13:27:55 -0700 [thread overview]
Message-ID: <20031022132755.7bfae6a0.akpm@osdl.org> (raw)
In-Reply-To: <3F967D66.9090601@cyberone.com.au>
Nick Piggin <piggin@cyberone.com.au> wrote:
>
>
>
> Oleg Drokin wrote:
>
> >Hello!
> >
> >
>
> Hi Oleg,
> 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?
I assume we're dealing with a non-fs request here.
next prev parent reply other threads:[~2003-10-22 20:27 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 [this message]
2003-10-23 2:21 ` Nick Piggin
2003-10-23 6:37 ` Oleg Drokin
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=20031022132755.7bfae6a0.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=green@linuxhacker.ru \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox