From: malahal@us.ibm.com
To: dm-devel@redhat.com
Subject: Re: Removing a failed device from LVM2/DM
Date: Tue, 1 Sep 2009 09:25:37 -0700 [thread overview]
Message-ID: <20090901162537.GA15197@us.ibm.com> (raw)
In-Reply-To: <1251821775.5459.21.camel@cail>
Alan D. Brunelle [Alan.Brunelle@hp.com] wrote:
> The vgreduce --removemissing helped a lot, thanks! But I still remain
> with all these error messages about the removed device. I tried
> everything again - using devices sda, sdab & sdad (failing sdab), and
> now every time I issue an LVM2/DM command I get all sorts of error
> messages about /dev/sdab failures. The 'pvs -a -o +devices' command not
> only puts out a ton - but also has a messed up display about the devices
> left working:
>
> # pvs -a -o +devices
> /dev/sdab: read failed after 0 of 2048 at 0: Input/output error
> Volume group name (null) has invalid characters
> Skipping volume group (null)
> ...
> Volume group name (null) has invalid characters
> Skipping volume group (null)
> Volume group name (null) has invalid characters
> Skipping volume group (null)
> PV VG Fmt Attr PSize PFree Devices
> /dev/sda vg lvm2 a- 271.34G 239.34G /dev/sda(0)
> /dev/sda vg lvm2 a- 271.34G 239.34G
> /dev/sda vg lvm2 a- 271.34G 239.34G
> /dev/sdad vg lvm2 a- 271.34G 271.34G
> /dev/sdad vg lvm2 a- 271.34G 271.34G
>
> Why the 5 lines for 2 devices?
>
> I've attached a log of commands & results.
>
> I have tried adding in "/dev/sdab" as being filtered out
> in /etc/lvm/lvm.conf but that doesn't change things. Here is first part
> of the output from lvm dumpconfig:
>
> # lvm dumpconfig
> devices {
> dir="/dev"
> scan="/dev"
> preferred_names=[]
> filter=["r|sdab|", "a/.*/"]
> cache_dir="/etc/lvm/cache"
> cache_file_prefix=""
> write_cache_state=1
> sysfs_scan=1
> md_component_detection=1
> md_chunk_alignment=1
> ignore_suspended_devices=0
> }
>
> but commands still error on /dev/sdab:
Did you remove the cache or ran vgscan?
/etc/lvm/lvm.conf recommends running 'vgscan -vvvv' to see what is going
on with filters.
next prev parent reply other threads:[~2009-09-01 16:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 15:16 Removing a failed device from LVM2/DM Alan D. Brunelle
2009-08-31 16:02 ` Takahiro Yasui
2009-08-31 16:24 ` malahal
2009-08-31 16:55 ` Alan D. Brunelle
2009-08-31 17:37 ` Takahiro Yasui
2009-09-01 16:16 ` Alan D. Brunelle
2009-09-01 16:25 ` malahal [this message]
2009-09-01 18:42 ` Alan D. Brunelle
2009-09-01 19:08 ` malahal
2009-09-01 20:57 ` Alan D. Brunelle
2009-09-01 22:47 ` malahal
2009-09-03 14:53 ` Alan D. Brunelle
2009-09-03 15:15 ` malahal
2009-09-23 4:59 ` Javier Barroso
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=20090901162537.GA15197@us.ibm.com \
--to=malahal@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.