From: Zdenek Kabelac <zkabelac@redhat.com>
To: Simon ELBAZ <selbaz@linagora.com>,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvdisplay "open" field computing
Date: Wed, 10 Jul 2019 15:32:02 +0200 [thread overview]
Message-ID: <d19f0e9f-d4a9-5362-34ef-4b33b5990d07@redhat.com> (raw)
In-Reply-To: <34f1f2af-cc02-6678-39d6-02323dd0236e@linagora.com>
Dne 10. 07. 19 v 13:54 Simon ELBAZ napsal(a):
> Hi Zdenek,
>
> Thanks for your feedback.
>
> The kernel version is:
>
> [root@panoramix ~]# uname -a
> Linux panoramix.ch-perrens.fr 2.6.32-573.12.1.el6.x86_64 #1 SMP Tue Dec 15
> 21:19:08 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>
Hi
So this is really a very historical kernel - released ~10 years back.
I'm afraid none is going to look out for the reasoning of any kernel bug....
It might be interesting to see if you get any reproducer to give you hints
how to avoid this happen (at least not easily).
> Jul 2 03:08:10 panoramix LVM(pri_ISCSIVG0_vg_obm)[18618]: INFO: Retry
> deactivating volume group vg_obm
>
> This is why I am trying to understand how the field is computed.
Simple rule applied here: DM devices in use (open_count > 0) cannot be
deactivated.
Occasionally there were 'race events' with udev - where device
which should have been otherwise unused has been asynchronously
opened by udev scanning rules - but that's like is not your case.
As you seems to have device open count higher permanently -
So if you are sure there is no running 'APP' after umount, that
keeps device open - it could be likely be some very old bug in kernel
with very high probably 99.99999% of being fixed ;)
Regards
Zdenek
next prev parent reply other threads:[~2019-07-10 13:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 9:47 [linux-lvm] lvdisplay "open" field computing Simon ELBAZ
2019-07-09 15:06 ` Zdenek Kabelac
2019-07-09 15:12 ` Simon ELBAZ
2019-07-09 15:15 ` Zdenek Kabelac
2019-07-09 15:27 ` Simon ELBAZ
[not found] ` <1f54874c-d4da-2579-955e-73e6caa8613b@linagora.com>
2019-07-10 10:51 ` Zdenek Kabelac
2019-07-10 11:54 ` Simon ELBAZ
2019-07-10 12:46 ` Simon ELBAZ
2019-07-10 13:32 ` Zdenek Kabelac [this message]
2019-07-10 13:37 ` Simon ELBAZ
2019-07-11 9:39 ` Simon ELBAZ
2019-07-11 15:17 ` Zdenek Kabelac
2019-07-12 12:38 ` Simon ELBAZ
2019-07-12 13:07 ` Zdenek Kabelac
2019-07-16 8:57 ` Simon ELBAZ
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=d19f0e9f-d4a9-5362-34ef-4b33b5990d07@redhat.com \
--to=zkabelac@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=selbaz@linagora.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).