From: Peter Rajnoha <prajnoha@redhat.com>
To: Gang He <ghe@suse.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] pvscan: /dev/sdc: open failed: No medium found
Date: Tue, 23 Apr 2019 17:24:35 +0200 [thread overview]
Message-ID: <9cd91b48-408b-f7a9-c4bc-df05d55376e6@redhat.com> (raw)
In-Reply-To: <5CBE9F89020000F900061398@prv1-mh.provo.novell.com>
On 4/23/19 7:15 AM, Gang He wrote:
> Hello List,
>
> One user complained this error message.
> The user has a usb sd card reader with no media present. When they issue a pvscan under lvm2-2.02.180 the device is opened which results in 'No medium found' being reported.
> But lvm2-2.02.120 did not do this (the device appears to get filtered out earlier). The customer views the 'No medium found' message as an issue/bug.
> Any suggest/comments for this error message?
>
> The detailed information is as below,
> lvm2 2.02.180-9.4.2
> OS: SLES12 SP4
> Kernel 4.12.14-95.3-default
> Hardware: HP ProLiant DL380 Gen10
>
> After upgrade from sles12SP3 to SP4, customer is reporting the following error message:
>
> # pvscan
> /dev/sdc: open failed: No medium found
> PV /dev/sdb VG Q11vg10 lvm2 [5.24 TiB / 2.00 TiB free]
> Total: 1 [5.24 TiB] / in use: 1 [5.24 TiB] / in no VG: 0 [0 ]
>
>
See also https://github.com/lvmteam/lvm2/issues/13
--
Peter
next prev parent reply other threads:[~2019-04-23 15:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 5:15 [linux-lvm] pvscan: /dev/sdc: open failed: No medium found Gang He
2019-04-23 14:27 ` David Teigland
2019-04-24 8:37 ` Zdenek Kabelac
2019-04-24 15:35 ` David Teigland
2019-04-24 19:43 ` Zdenek Kabelac
2019-04-23 15:24 ` Peter Rajnoha [this message]
2019-04-24 3:23 ` Gang He
[not found] ` <20190424150858.GA3218@redhat.com>
2019-04-29 9:16 ` Gang He
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=9cd91b48-408b-f7a9-c4bc-df05d55376e6@redhat.com \
--to=prajnoha@redhat.com \
--cc=ghe@suse.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).