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

vmware net_device trans_start

VMWare Workstation 12 and Kernel 4.7 When recompiling vmware kernel modules on a kernel 4.7, I get this error:

/tmp/modconfig-xrrZGZ/vmnet-only/netif.c:468:7: error: ‘struct net_device’ has no member named ‘trans_start’; did you mean ‘mem_start’?     dev->trans_start = jiffies;
This seems to be an already encountered problem: http://rglinuxtech.com/?p=1746http://ferenc.homelinux.com/?p=356 I choosed to replace the line, instead of deleting it.

- dev->trans_start = jiffies; + netif_trans_update(dev); I also noted that I had to re-tar the modified sources instead of leaving them untared, because the compilation process only takes the archives. 
On precedent editions of these files, I just left the modified folders "vmnet-only/" and "vmmon-only/" expanded without the need to re-tar them.


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 selectThere will be no creation of Workflow and Issue Scheme that I need to cleanup

This fea…

vmware workstation 12 unable to load libvmwareui.so

Using VMWare Workstation on ArchLinux, it suddenly refused to launch.
when inspecting the logs, which BTW are in /tmp/vmware-<id>, I see:

2015-12-11T17:41:54.442+03:00| appLoader| I125: Log for appLoader pid=1727 version=12.0.1 build=build-3160714 option=Release
2015-12-11T17:41:54.442+03:00| appLoader| I125: The process is 64-bit.
2015-12-11T17:41:54.442+03:00| appLoader| I125: Host codepage=UTF-8 encoding=UTF-8
2015-12-11T17:41:54.442+03:00| appLoader| I125: Host is unknown
2015-12-11T17:41:54.448+03:00| appLoader| W115: HostinfoReadDistroFile: Cannot work with empty file.
2015-12-11T17:41:54.448+03:00| appLoader| W115: HostinfoOSData: Error: no distro file found
2015-12-11T17:41:54.448+03:00| appLoader| I125: Invocation: "/usr/lib/vmware/bin/vmware-modconfig --launcher=/usr/bin/vmware-modconfig --appname=VMware Workstation --icon=vmware-workstation"
2015-12-11T17:41:54.448+03:00| appLoader| I125: Calling: "/usr/lib/vmware/bin/vmware-modconfig --launcher=/usr/bin/vmware…