From: "Gang He" <ghe@suse.com>
To: linux-lvm@redhat.com, teigland@redhat.com
Subject: Re: [linux-lvm] pvscan: /dev/sdc: open failed: No medium found
Date: Mon, 29 Apr 2019 03:16:24 -0600 [thread overview]
Message-ID: <5CC6C0E8020000F900062DC8@prv1-mh.provo.novell.com> (raw)
In-Reply-To: <20190424150858.GA3218@redhat.com>
Hello David,
Sorry for delayed reply.
the verbose log (lvm2-2.02.180) looks like,
#device/dev-cache.c:763 Found dev 11:0 /dev/disk/by-id/ata-TSSTcorp_DVDWBD_SH-B123L_R84A6GDC10003F - new alias.
#device/dev-cache.c:763 Found dev 11:0 /dev/disk/by-label/SLE-12-SP4-Server-DVD-x86_640456 - new alias.
#device/dev-cache.c:763 Found dev 11:0 /dev/disk/by-path/pci-0000:00:1f.2-ata-2 - new alias.
#device/dev-cache.c:763 Found dev 11:0 /dev/disk/by-uuid/2018-11-07-14-08-50-00 - new alias.
#device/dev-cache.c:763 Found dev 11:0 /dev/dvd - new alias.
#device/dev-cache.c:763 Found dev 11:0 /dev/dvdrw - new alias.
#cache/lvmetad.c:1420 Asking lvmetad for complete list of known PVs
#device/dev-io.c:609 Opened /dev/sda RO O_DIRECT
#device/dev-io.c:359 /dev/sda: size is 268435456 sectors
#device/dev-io.c:658 Closed /dev/sda
#filters/filter-partitioned.c:37 /dev/sda: Skipping: Partition table signature found
#filters/filter-type.c:27 /dev/cdrom: Skipping: Unrecognised LVM device type 11
#device/dev-io.c:609 Opened /dev/sda1 RO O_DIRECT
#device/dev-io.c:359 /dev/sda1: size is 4206592 sectors
#device/dev-io.c:658 Closed /dev/sda1
#filters/filter-mpath.c:196 /dev/sda1: Device is a partition, using primary device sda for mpath component detection
#device/dev-io.c:336 /dev/sda1: using cached size 4206592 sectors
#filters/filter-persistent.c:346 filter caching good /dev/sda1
#device/dev-io.c:609 Opened /dev/root RO O_DIRECT
#device/dev-io.c:359 /dev/root: size is 264226816 sectors
#device/dev-io.c:658 Closed /dev/root
#filters/filter-mpath.c:196 /dev/root: Device is a partition, using primary device sda for mpath component detection
#device/dev-io.c:336 /dev/root: using cached size 264226816 sectors
#filters/filter-persistent.c:346 filter caching good /dev/root
#device/dev-io.c:567 /dev/sdb: open failed: No medium found <<== here
#device/dev-io.c:343 <backtrace>
#filters/filter-usable.c:32 /dev/sdb: Skipping: dev_get_size failed
#toollib.c:4377 Processing PVs in VG #orphans_lvm2
#locking/locking.c:331 Dropping cache for #orphans.
#misc/lvm-flock.c:202 Locking /run/lvm/lock/P_orphans RB
#misc/lvm-flock.c:100 _do_flock /run/lvm/lock/P_orphans:aux WB
#misc/lvm-flock.c:47 _undo_flock /run/lvm/lock/P_orphans:aux
#misc/lvm-flock.c:100 _do_flock /run/lvm/lock/P_orphans RB
#cache/lvmcache.c:751 lvmcache has no info for vgname "#orphans".
#metadata/metadata.c:3764 Reading VG #orphans_lvm2
#locking/locking.c:331 Dropping cache for #orphans.
#misc/lvm-flock.c:70 Unlocking /run/lvm/lock/P_orphans
#misc/lvm-flock.c:47 _undo_flock /run/lvm/lock/P_orphans
#cache/lvmcache.c:751 lvmcache has no info for vgname "#orphans".
#locking/locking.c:331 Dropping cache for #orphans.
Thanks
Gang
>>> On 4/24/2019 at 11:08 pm, in message <20190424150858.GA3218@redhat.com>, David
Teigland <teigland@redhat.com> wrote:
> On Tue, Apr 23, 2019 at 09:23:29PM -0600, Gang He wrote:
>> Hello Peter and David,
>>
>> Thank for your quick responses.
>> How do we handle this behavior further?
>> Fix it as an issue, filter this kind of disk silently.
>> or keep the current error message printing, looking a bit unfriendly, but
> the logic is not wrong.
>
> Hi,
>
> I'd like to figure out what the old code was doing differently to avoid
> this. Part of the problem is that I don't have a device that reports
> these same errors. Could you send me the output of pvscan -vvvv so I can
> see which open is causing the error?
> Thanks
prev parent reply other threads:[~2019-04-29 9:16 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
2019-04-24 3:23 ` Gang He
[not found] ` <20190424150858.GA3218@redhat.com>
2019-04-29 9:16 ` Gang He [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=5CC6C0E8020000F900062DC8@prv1-mh.provo.novell.com \
--to=ghe@suse.com \
--cc=linux-lvm@redhat.com \
--cc=teigland@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).