linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Abhishek Agarwal <mragarwal.developer@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvm commands hanging when run from inside a kubernetes pod
Date: Mon, 6 Jun 2022 17:01:15 +0530	[thread overview]
Message-ID: <CAM3OQJEJCV_ozKjHS2FguUsnZXD37eK9YBExjRT-ZAdJGUp_TA@mail.gmail.com> (raw)
In-Reply-To: <Yp2mZGmhFD23XQcL@itl-email>


[-- Attachment #1.1: Type: text/plain, Size: 1653 bytes --]

Hey Demi, can you explain how it will help to solve the problem? I'm
actually not aware of that much low-level stuff but would like to learn
about it. Also, can you provide a few references for it on how I can use it?

Thanks

On Mon, 6 Jun 2022 at 12:32, Demi Marie Obenour <demi@invisiblethingslab.com>
wrote:

> On Mon, Jun 06, 2022 at 11:19:47AM +0530, Abhishek Agarwal wrote:
> > 1. Yes, use_lvmetad is 0, and its systemd units for it are
> stopped/disabled.
> > 2. Yes, everything on the host machine i.e(/proc, /sys etc) are getting
> > mounted on the pod.
> >
> > *ubuntu@ip-172-31-89-47*:*~*$ kubectl exec -it openebs-lvm-node-v6jrb -c
> > openebs-lvm-plugin  -n kube-system -- sh
> >
> > # ls
> >
> > bin  boot  dev etc  home  host  lib  lib32  lib64  libx32  media  mnt opt
> > plugin  proc  root  run  sbin  srv  sys  tmp  usr var
> >
> > # cd /host
> >
> > # ls
> >
> > bin  boot  dev etc  home  lib lib32  lib64  libx32  lost+found  media
> mnt
> > opt  proc  root  run  sbin  snap srv  sys  tmp  usr  var
> >
> > #
> > 3. The detail output of `strace -f -ttt` command:
> > https://pastebin.com/raw/VFyXLNaC
>
> I suggest bind-mounting the host’s D-Bus socket into the container and
> using systemd’s D-Bus API to run the LVM commands on the host.  This
> will avoid the problems you are having.
> --
> Sincerely,
> Demi Marie Obenour (she/her/hers)
> Invisible Things Lab
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://listman.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>

[-- Attachment #1.2: Type: text/html, Size: 2675 bytes --]

[-- Attachment #2: Type: text/plain, Size: 202 bytes --]

_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

  reply	other threads:[~2022-06-07  7:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-27  7:02 [linux-lvm] lvm commands hanging when run from inside a kubernetes pod Abhishek Agarwal
2022-05-30 11:55 ` Roger Heflin
2022-05-31 18:50   ` Abhishek Agarwal
2022-06-01  7:26     ` Demi Marie Obenour
2022-06-01  8:28       ` Abhishek Agarwal
2022-06-02 11:04         ` Roger Heflin
2022-06-06  5:49           ` Abhishek Agarwal
2022-06-06  7:01             ` Demi Marie Obenour
2022-06-06 11:31               ` Abhishek Agarwal [this message]
2022-06-07 17:42                 ` Demi Marie Obenour
2022-06-06  7:02             ` Bernd Eckenfels
2022-06-02 19:00         ` Nir Soffer
2022-05-30 15:15 ` Zdenek Kabelac
2022-05-30 15:15   ` Zdenek Kabelac

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=CAM3OQJEJCV_ozKjHS2FguUsnZXD37eK9YBExjRT-ZAdJGUp_TA@mail.gmail.com \
    --to=mragarwal.developer@gmail.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).