From: Martin Schlemmer <azarah@nosferatu.za.org>
To: Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>
Subject: Device-mapper quary
Date: Sat, 05 Mar 2005 17:48:30 +0200 [thread overview]
Message-ID: <1110037710.8842.2.camel@nosferatu.lan> (raw)
[-- Attachment #1: Type: text/plain, Size: 991 bytes --]
Hi,
I have been getting the following in my logs recently (just after
bootup):
-----
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex
Buffer I/O error on device sda3, logical block 308367488
Buffer I/O error on device sda3, logical block 308367489
Buffer I/O error on device sda3, logical block 308367490
Buffer I/O error on device sda3, logical block 308367491
Buffer I/O error on device sda3, logical block 308367492
Buffer I/O error on device sda3, logical block 308367493
Buffer I/O error on device sda3, logical block 308367494
Buffer I/O error on device sda3, logical block 308367495
Buffer I/O error on device sda3, logical block 308367488
Buffer I/O error on device sda3, logical block 308367489
-----
I checked sda though, and it seems fine (badblocks, e2fsck, etc). sda
(and in theory sda3) is part of a device-mapper stripe array ....
Thanks,
--
Martin Schlemmer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2005-03-05 15:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1110037710.8842.2.camel@nosferatu.lan \
--to=azarah@nosferatu.za.org \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome