From: Peter <peter.spamcatcher@rimuhosting.com>
To: xen-devel@lists.xensource.com
Subject: Buffer I/O error on device nbd0
Date: Sat, 06 Aug 2005 22:53:04 +1200 [thread overview]
Message-ID: <42F49690.9030908@rimuhosting.com> (raw)
Hi. We get the errors below in the kernel logs.
WARNING: Kernel Errors Present
Buffer I/O error on device nbd0, ...: 27 Time(s)
Buffer I/O error on device nbd16,...: 3 Time(s)
end_request: I/O error, dev nbd0, secto...: 13 Time(s)
end_request: I/O error, dev nbd1, secto...: 7 Time(s)
end_request: I/O error, dev nbd10, sect...: 7 Time(s)
I see someone else has reported this error message. E.g. see:
http://lists.xensource.com/archives/html/xen-devel/2004-09/msg00348.html
I'm not sure what we are running in /etc/init.d that could be starting
something that triggers this error. And I don't believe we see the same
error when we use the same file system under UML (but that may be
because we have different kernel options enabled).
Has there been any further thought as to what triggers these error
messages? Or do you have any advice on what we can do to try and avoid
them?
Regards, Peter
http://rimuhosting.com - Xen VPS Hosting
next reply other threads:[~2005-08-06 10:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-06 10:53 Peter [this message]
2005-08-07 8:44 ` Buffer I/O error on device nbd0 Keir Fraser
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=42F49690.9030908@rimuhosting.com \
--to=peter.spamcatcher@rimuhosting.com \
--cc=xen-devel@lists.xensource.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.