linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Karl" <rmvzj001@sneakemail.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] read_intr errors
Date: Wed, 17 Oct 2001 15:27:31 -0700	[thread overview]
Message-ID: <134714172.1003357674676.JavaMail.root@boots> (raw)

On Wed, Oct 17, 2001 at 02:20:23PM -0700, Erick Calder e@arix.com XXXXXXXXXXXXXXXXXXXX wrote:
> I haven't tried that but if I unmount the filesystem and check it:
> 
> # umount /dev/LVM/mp3z
> # fsck /dev/LVM/mp3z
> 
> it comes up clean....  is that not an equivalent test?

Not sure. I don't think fsck checks every block. The errors I saw certainly
were consistant in location on the LVM, but there were no corrisponding errors
on the hardware. You can try the following

cat /dev/vg.../lvol/... >/dev/null # where vg and lvol are appropriate for your file system.

cat /dev/hd... # were hd is your physical device. If you get errors on one and
# not the other, you too will be an example of the problem we are talking about.

-- 
Karl Hakimian

             reply	other threads:[~2001-10-17 22:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-17 22:27 Karl [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-24 11:36 [linux-lvm] read_intr errors Karl
2001-10-17 20:21 Karl
2001-10-17 21:20 ` Erick Calder
2001-10-18  0:09   ` Wolfgang Weisselberg
2001-10-16 21:40 [linux-lvm] Remount a LVM Vol after a system crash Heinz J . Mauelshagen
2001-10-17  9:27 ` [linux-lvm] read_intr errors Erick Calder
2001-10-17 14:29   ` Patrick Caulfield
2001-10-17 20:08     ` Erick Calder
2001-10-18  7:42       ` Patrick Caulfield
2001-10-23 23:19         ` Erick Calder
2001-10-24  4:25           ` Patrick Caulfield
2001-10-26  2:13             ` Erick Calder
2001-10-26  3:29               ` Patrick Caulfield
2001-10-26 16:16                 ` Erick Calder
2001-10-30  2:55                   ` Patrick Caulfield

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=134714172.1003357674676.JavaMail.root@boots \
    --to=rmvzj001@sneakemail.com \
    --cc=linux-lvm@sistina.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).