From: Dave Wysochanski <dwysocha@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] pvscan/vgscan/lvscan error
Date: Wed, 28 Feb 2007 13:02:39 -0500 [thread overview]
Message-ID: <1172685760.4270.3.camel@linux-cxyg.rtp.netapp.com> (raw)
In-Reply-To: <45D8A380.6050807@cesca.es>
On Sun, 2007-02-18 at 20:05 +0100, Jordi Prats wrote:
> Hello,
> I've found more errors using lvm commands. This time using vgdisplay and
> lvdisplay:
>
> # vgdisplay
> /dev/sdb: read failed after 0 of 4096 at 0: Input/output error
> /dev/sde: read failed after 0 of 4096 at 0: Input/output error
> /dev/sdf: read failed after 0 of 4096 at 0: Input/output error
> /dev/sdg: read failed after 0 of 4096 at 0: Input/output error
> /dev/sdi: read failed after 0 of 4096 at 0: Input/output error
> /dev/sdk: read failed after 0 of 4096 at 0: Input/output error
> /dev/sdl: read failed after 0 of 4096 at 0: Input/output error
> /dev/sdp: read failed after 0 of 4096 at 0: Input/output error
> --- Volume group ---
> (...)
>
> # lvdisplay
> /dev/sdb: read failed after 0 of 4096 at 0: Input/output error
> /dev/sde: read failed after 0 of 4096 at 0: Input/output error
> /dev/sdf: read failed after 0 of 4096 at 0: Input/output error
> /dev/sdg: read failed after 0 of 4096 at 0: Input/output error
> /dev/sdi: read failed after 0 of 4096 at 0: Input/output error
> /dev/sdk: read failed after 0 of 4096 at 0: Input/output error
> /dev/sdl: read failed after 0 of 4096 at 0: Input/output error
> /dev/sdp: read failed after 0 of 4096 at 0: Input/output error
> --- Logical volume ---
> (...)
>
> I don't know what is causing this. Anyone can help me with this problem?
>
> Thank you!
> Jordi
>
What kind of storage do you have?
This might happen if you have an active/passive storage array. The
passive paths won't accept I/O, but will show up in a device list. LVM
(and other processes/threads) tries to do I/O to all devices (unless
they are filtered out in /etc/lvm.conf), and so you get I/O errors.
> Jordi Prats wrote:
> > Hi all,
> > I've found that all vgscan is giving me an error. This is the output:
> >
> > # vgscan -v
> > Wiping cache of LVM-capable devices
> > Wiping internal VG cache
> > Reading all physical volumes. This may take a while...
> > Finding all volume groups
> > /dev/dm-4: read failed after 0 of 4096 at 12989693952: Input/output error
> > /dev/dm-4: read failed after 0 of 4096 at 0: Input/output error
> > Finding volume group "padicat"
> > Found volume group "padicat" using metadata type lvm2
> > Finding volume group "vg_bbdd"
> > Found volume group "vg_bbdd" using metadata type lvm2
> > Finding volume group "vg_ordal"
> > Found volume group "vg_ordal" using metadata type lvm2
> >
> > Any idea what this "Input/output error" on /dev/dm-4 does it means? What
> > is causing this error?
> >
> > Thank you!
> >
>
prev parent reply other threads:[~2007-02-28 18:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 8:48 [linux-lvm] pvscan/vgscan/lvscan error Jordi Prats
2007-02-18 19:05 ` Jordi Prats
2007-02-28 18:02 ` 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=1172685760.4270.3.camel@linux-cxyg.rtp.netapp.com \
--to=dwysocha@redhat.com \
--cc=linux-lvm@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 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).