linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Simon ELBAZ <selbaz@linagora.com>
To: Zdenek Kabelac <zkabelac@redhat.com>,
	LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvdisplay "open" field computing
Date: Tue, 16 Jul 2019 10:57:00 +0200	[thread overview]
Message-ID: <5dfb4dd2-3cd8-2bd5-e6a7-c484995655c8@linagora.com> (raw)
In-Reply-To: <adba2e2b-add1-6a3e-fe85-334369e59735@redhat.com>

Hi Zdenek,

Finally, it was veeamsnap that was mounting the LV.

It is a kernel module used by Veeambackup.

This is why - as you explained me - I could not see it with lsof command.

Regards

Simon

On 12/07/2019 15:07, Zdenek Kabelac wrote:
> Dne 12. 07. 19 v 14:38 Simon ELBAZ napsal(a):
>> Hi,
>>
>  root@sympa:~# swapon /dev/sympa-vg/swap_1
>> root@sympa:~# lvdisplay
>> ...
>>
>>    --- Logical volume ---
>>    LV Path                /dev/sympa-vg/swap_1
>>    LV Name                swap_1
>>    VG Name                sympa-vg
>>    LV UUID                1b59OW-M2yW-PuI1-QN5t-pN0w-6Akl-AnJnNh
>>    LV Write Access        read/write
>>    LV Creation host, time sympa, 2019-07-10 11:06:42 +0200
>>    LV Status              available
>>    # open                 2
>>    LV Size                <1,99 GiB
>>    Current LE             509
>>    Segments               1
>>    Allocation             inherit
>>    Read ahead sectors     auto
>>    - currently set to     256
>>    Block device           254:1
>>
>> I wonder if there is a similar tool for regular filesystem types.
>>
>
> Hi
>
>
> See:  mount
>
> or
>
> /proc/self/mountinfo
>
>
> Regards
>
> Zdenek
>
-- 
Simon Elbaz
@Linagora
Mob: +33 (0) 6 38 99 18 34
Tour Franklin 31ème étage
100/101 Quartier Boieldieu
92042 La Défense
FRANCE

      reply	other threads:[~2019-07-16  8:57 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
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 [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=5dfb4dd2-3cd8-2bd5-e6a7-c484995655c8@linagora.com \
    --to=selbaz@linagora.com \
    --cc=linux-lvm@redhat.com \
    --cc=zkabelac@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).