Gecko [ theprintave.ca ]

Linux webserver 6.8.0-49-generic #49~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Nov 6 17:42:15 UTC 2 x86_64
Apache/2.4.52 (Ubuntu)
Server IP : 192.168.1.1 & Your IP : 3.147.72.31
Domains : Cant Read [ /etc/named.conf ]
User : www-data

Name	Size	Permission	Date
changelog.Debian.gz	2 KB	-rw-r--r--	2022-02-16 17:06
copyright	4.54 KB	-rw-r--r--	2021-05-19 10:19
lvm-disk-reading.txt.gz	3.52 KB	-rw-r--r--	2021-01-08 09:10
lvm2-raid.txt.gz	8.35 KB	-rw-r--r--	2021-01-08 09:10
lvm_fault_handling.txt.gz	4.05 KB	-rw-r--r--	2021-01-08 09:10
lvmetad_design.txt.gz	4.38 KB	-rw-r--r--	2021-01-08 09:10
lvmpolld_overview.txt	3.22 KB	-rw-r--r--	2021-01-08 09:10
pvmove_outline.txt	1.71 KB	-rw-r--r--	2021-01-08 09:10
refactoring.txt.gz	1.61 KB	-rw-r--r--	2021-01-08 09:10
tagging.txt.gz	1.95 KB	-rw-r--r--	2021-01-08 09:10
testing.txt	1.18 KB	-rw-r--r--	2021-01-08 09:10
udev_assembly.txt	3.97 KB	-rw-r--r--	2021-01-08 09:10
unit-tests.txt.gz	2.45 KB	-rw-r--r--	2021-01-08 09:10

Rename

Here's how I test new LVM2 builds without interfering with the stable
LVM2 that is running the LV's on my development box.

1) Create a set of loopback devices.

2) Create a new directory to contain the LVM2 configuration files for
   this setup.  (I use /etc/lvm_loops)

3) Write a suitable lvm.conf file, this goes in the directory you just
   created.  eg, my /etc/lvm_loops/lvm.conf looks like:

log {
        file="/tmp/lvm2_loop.log"
        level=9
        verbose=0
        overwrite=1
   }

devices {
        scan = "/dev"
        filter = ["a/loop/", "r/.*/"]
   }

The important thing to note is the devices section which makes sure
   that only the loopback devices are considered for LVM2 operations.

4) When you want to use this test setup just set the environment
   variable LVM_SYSTEM_DIR to point to your config directory
   (/etc/lvm_loops in my case).

5) It's a good idea to do a vgscan to initialise the filters:

export LVM_SYSTEM_DIR=/etc/lvm_loops
   ./lvm vgscan

where ./lvm is the new build of LVM2 that I'm trying out.

7) Test away.  Make sure that you are explicit about which lvm
   executable you want to execute (eg, ./lvm if you are in
   LVM2/tools).