Dne 23.6.2016 v 20:02 Chris Friesen napsal(a):
On 06/23/2016 11:21 AM, Zdenek Kabelac wrote:
Dne 23.6.2016 v 18:35 Chris Friesen napsal(a):
[root@centos7 centos]# vgscan --mknodes
Configuration setting "snapshot_autoextend_percent" invalid. It's not part
of any section.
Configuration
On 06/23/2016 11:21 AM, Zdenek Kabelac wrote:
Dne 23.6.2016 v 18:35 Chris Friesen napsal(a):
[root@centos7 centos]# vgscan --mknodes
Configuration setting "snapshot_autoextend_percent" invalid. It's not part
of any section.
Configuration setting "snapshot_autoextend_threshold" invalid.
Dne 23.6.2016 v 18:35 Chris Friesen napsal(a):
On 06/23/2016 02:34 AM, Zdenek Kabelac wrote:
Dne 22.6.2016 v 16:52 Chris Friesen napsal(a):
On 06/22/2016 03:23 AM, Zdenek Kabelac wrote:
Dne 21.6.2016 v 17:22 Chris Friesen napsal(a):
I'm using the stock CentOS7 version, I think.
LVM
On 06/23/2016 02:34 AM, Zdenek Kabelac wrote:
Dne 22.6.2016 v 16:52 Chris Friesen napsal(a):
On 06/22/2016 03:23 AM, Zdenek Kabelac wrote:
Dne 21.6.2016 v 17:22 Chris Friesen napsal(a):
I'm using the stock CentOS7 version, I think.
LVM version: 2.02.130(2)-RHEL7 (2015-12-01)
Library
I'm using the stock CentOS7 version, I think.
LVM version: 2.02.130(2)-RHEL7 (2015-12-01)
Library version: 1.02.107-RHEL7 (2015-12-01)
Driver version: 4.33.0
So are you saying that nobody should run "vgscan --mknodes" on a system where
udev is managing the symlinks?
Personally, I
Found it. /usr/lib/udev/rules.d/11-dm-lvm.rules is what makes the
/dev// symlink for normal devices, but for a thin pool with a thin
volume in it it will exit without making a symlink because
DM_UDEV_DISABLE_SUBSYSTEM_RULES_FLAG=1 is set.
Given that both vgmknodes and the udev rules come
It appears that "vgscan --mknodes" also creates this symlink, and creates it
pointing to /dev/mapper/ instead of to /dev/dm-X like udev does.
controller-1:/dev# vgscan -v --mknodes
Wiping cache of LVM-capable devices
Wiping internal VG cache
Reading all physical volumes. This may
