From: Mike Anderson <andmike@us.ibm.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Buffer I/O errors
Date: Tue, 2 May 2006 14:14:46 -0700 [thread overview]
Message-ID: <20060502211446.GA30834@us.ibm.com> (raw)
In-Reply-To: <4454A5CC.20108@telkomsa.net>
Niel Lambrechts <antispam@telkomsa.net> wrote:
> Buffer I/O error on dm-0
> Lost page write due to I/O error
> reiserfs: dm-0 journal write error in flush_commit_list
>
There should be a few scsi error messages in the log prior to "Buffer I/O
error on dm-0" that would provide info on why the scsi command did not
complete. This will answer all your failure isolation questions, but it
will help narrow it down to the next level.
-andmike
--
Michael Anderson
andmike@us.ibm.com
prev parent reply other threads:[~2006-05-02 21:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-30 11:55 Buffer I/O errors Niel Lambrechts
2006-05-02 21:14 ` Mike Anderson [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=20060502211446.GA30834@us.ibm.com \
--to=andmike@us.ibm.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.