[linux-lvm] [dm-crypt] LVM on LUKS: volumes missing

Ondrej Kozina okozina at redhat.com
Thu Jun 2 13:22:19 UTC 2016

On 05/31/2016 03:17 PM, fauno wrote:
> #libdm-config.c:863       Setting activation/monitoring to 0
> #lvmcmdline.c:1093         Processing: pvscan -vvvv --cache
> /dev/mapper/system
> #lvmcmdline.c:1096         O_DIRECT will be used
> #libdm-config.c:799       Setting global/locking_type to 1
> #libdm-config.c:799       Setting global/wait_for_locks to 1
> #locking/locking.c:242       File-based locking selected.
> #libdm-config.c:768       Setting global/locking_dir to /run/lock/lvm
> #libdm-config.c:863       Setting global/prioritise_write_locks to 1
> #locking/file_locking.c:236       Locking /run/lock/lvm/P_global RB
> #locking/file_locking.c:141         _do_flock /run/lock/lvm/P_global:aux WB
> #locking/file_locking.c:51         _undo_flock /run/lock/lvm/P_global:aux
> #locking/file_locking.c:141         _do_flock /run/lock/lvm/P_global RB
> #pvscan.c:150     Using physical volume(s) on command line
> #device/dev-cache.c:347         /dev/mapper/system: Added to device cache
> #locking/file_locking.c:74       Unlocking /run/lock/lvm/P_global
> #locking/file_locking.c:51         _undo_flock /run/lock/lvm/P_global
>   Command failed with status code 5.

This is very strange pvscan -vvvv output. Reading upstream lvm2 code, it 
doesn't make much sense to me. Most notably I can't see full error path. 
Could it be that pvscan -vvvv output was cut off somehow?


More information about the linux-lvm mailing list