Skip to main content

lvm and PV listing

Goal

I would like to list the PVs involved in a VG. Neither "vgs" nor "vgdisplay" tells me. I need that information in order to install and clone an existing Debian using LVM and want to have the same LVM configuration.

Recipe

The "vgs" output:
 root@maila:~# vgs   VG    #PV #LV #SN Attr   VSize   VFree     disk0   1   1   0 wz--n- 931,51G 520,00M   disk1   1   2   0 wz--n- 447,13G 397,13G            
The "pvs" output:
 root@maila:~# pvs   PV         VG    Fmt  Attr PSize   PFree     /dev/md1   disk1 lvm2 a-   447,13G 397,13G   /dev/md2   disk0 lvm2 a-   931,51G 520,00M            
How to read it:
  • There is only one PV per VG
  • "md1" belongs to the VG disk1
  • "md2" belongs to the VG disk0
If the output where:
 root@maila:~# pvs   PV         VG       /dev/md1   disk1    /dev/md2   disk0          /dev/md3   disk1    /dev/md4   disk0          /dev/md5   disk1    /dev/md6   disk0          /dev/md7   disk1    /dev/md8   disk0             
Then that would mean:
  • There are 4 PVs per VG
  • "md1", "md3", "md5" and "md7" belong to the VG disk1
  • "md2", "md4", "md6" and "md8" belong to the VG disk0

Comments

Popular posts from this blog

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='https://ngx.rktmb.org/foo' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href='https://ngx.rktmb.org/foo'" parameter. npm run build --base-href='https://ngx.rktmb.org/foo did not set the base href in indext.html After looking for a while, I found https://github.com/angular/angular-cli/issues/13560 where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='https://ngx.rktmb.org/foo&

dockerfile multiline to file

Outputing a multiline string from Dockerfile I motsly use a Dockerfile by sourcing from a base ditribution: CentOS or Debian. But I also have a local mirror and would like to use it for packages installation. Espacially on CentOS it is about many lines to write to the /etc/yum.repos.d/CentOS-Base.repo file. Easiest way: one RUN per line The first method that comes in mind is to issue one RUN per line to write. Here you are: RUN echo "[base] " > /etc/yum.repos.d/CentOS-Base.repo RUN echo "name=CentOS-$releasever - Base " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "baseurl=ftp://packages-infra.mg.rktmb.org/pub/centos/7/base-reposync-7 " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "gpgcheck=0 &quo

Jira workflow for new projects

Associated workflow creation I'm a Jira Cloud user and begining from some version 6, I noticed that when I create a project, it automatically creates a Workflow and Issue Scheme that is prepended by the project key and which is a copy of the default scheme. I always had to make a cleanup after creating a project. Default workflow for new projects I also miss a feature that would allow me to make a custom workflow (and globally custom project setting) the default for new projects I create. Solution: Create with shared configuration While searching, I noticed that with Jira Cloud which is version 7.1.0 at the time I write, there is a link at the bottom of the "Create project" wizard: "Create with shared configuration" will allow me to select the project I want the new one to share configuration with. The new created project will use the same configuration as the project I select There will be no creation of Workflow and Issue Scheme that