From: Dave Wysochanski <dwysocha@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: RE: Multipath issues with kernel device errors
Date: Thu, 04 Oct 2007 14:49:06 -0400 [thread overview]
Message-ID: <1191523746.4406.15.camel@linux-cxyg> (raw)
In-Reply-To: <8CED8CEBA23FC0409E1A3009F7F47BE5024711B7@exchange.g2switchworks.com>
On Wed, 2007-08-29 at 11:58 -0500, Jeffry Bilder wrote:
> Are the errors in the kernel log normal:
>
>
> Aug 28 10:30:15 rac02 kernel: end_request: I/O error, dev sdf, sector 513824
> Aug 28 10:30:15 rac02 kernel: Buffer I/O error on device sdf, logical block 64228
> Aug 28 10:30:15 rac02 kernel: Buffer I/O error on device sdf, logical block 64229
> Aug 28 10:30:15 rac02 kernel: Buffer I/O error on device sdf, logical block 64230
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64231
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64232
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64233
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64234
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64235
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64236
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64237
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64238
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64239
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64240
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64241
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64242
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64243
> Aug 28 10:30:16 rac02 kernel: Device sdf not ready.
> Aug 28 10:30:16 rac02 kernel: end_request: I/O error, dev sdf, sector 513824
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64228
> Aug 28 10:30:16 rac02 kernel: Device sdf not ready.
> Aug 28 10:30:16 rac02 kernel: end_request: I/O error, dev sdf, sector 513824
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64228
> Aug 28 10:30:16 rac02 kernel: Device sdf not ready.
> Aug 28 10:30:16 rac02 kernel: end_request: I/O error, dev sdf, sector 514064
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64258
> Aug 28 10:30:16 rac02 kernel: Device sdf not ready.
> Aug 28 10:30:16 rac02 kernel: end_request: I/O error, dev sdf, sector 513680
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64210
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64211
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64212
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64213
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64214
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64215
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64216
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64217
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64218
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64219
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64220
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64221
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64222
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64223
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64224
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64225
> Aug 28 10:30:16 rac02 kernel: Device sdf not ready.
>
>
Yes unfortunately these are normal for this array and any array that has
passive paths. There are fixes needed in the kernel to eliminate these
errors.
prev parent reply other threads:[~2007-10-04 18:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8CED8CEBA23FC0409E1A3009F7F47BE502471065@exchange.g2switchworks.com>
[not found] ` <1188333723.12737.7.camel@linuxchandra>
[not found] ` <8CED8CEBA23FC0409E1A3009F7F47BE502471086@exchange.g2switchworks.com>
[not found] ` <1188338656.12737.18.camel@linuxchandra>
2007-08-29 6:14 ` Multipath issues with kernel device errors Hannes Reinecke
2007-08-29 13:29 ` Jeffry Bilder
2007-08-29 16:58 ` Jeffry Bilder
2007-10-04 18:49 ` Dave Wysochanski [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=1191523746.4406.15.camel@linux-cxyg \
--to=dwysocha@redhat.com \
--cc=dm-devel@redhat.com \
/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.