All of lore.kernel.org
 help / color / mirror / Atom feed
From: fauno <fauno@partidopirata.com.ar>
To: linux-lvm@redhat.com
Cc: okozina@redhat.com
Subject: Re: [linux-lvm] [dm-crypt] LVM on LUKS: volumes missing
Date: Tue, 31 May 2016 10:17:26 -0300	[thread overview]
Message-ID: <574D8EE6.8020903@partidopirata.com.ar> (raw)
In-Reply-To: <dc632a53-2e8a-651e-5c95-fcf467d6628d@redhat.com>


[-- Attachment #1.1: Type: text/plain, Size: 5083 bytes --]

On 31/05/16 04:53, Ondrej Kozina wrote:
> Hi fauno,
> 
> provided the driver was unlocked successfully it seems unrelated to
> cryptsetup/LUKS to me. Could we move the discussion to lvm mail list?

ok :)

> On 05/30/2016 11:54 PM, fauno wrote:
>> Hi, maybe I'm too shocked but I couldn't find anything on this issue :)
>>
>> I have a fully encrypted HD using the LVM on LUKS method from
>> ArchWiki[^0], with the LUKS header and key file on an external device.
>>
>> Today I started having some disk failures (root remounted ro, xfs
>> partition giving errors), and after I decided to reboot to run fsck, I
>> can't find anything.
> 
> Could you paste here output of pvscan -vvvv --cache
> /dev/mapper/insert_the_unlocked_device_name?

#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.

> Together with your
> /etc/lvm/lvm.conf file? If it's a device with rootfs we're talking about
> you will most probably have to extract /etc/lvm/lvm.conf file from
> initramfs image.

this is the lvm.conf from the initramfs (removed comments)


config {
	checks = 1
	abort_on_errors = 0
	profile_dir = "/etc/lvm/profile"
}
devices {
	dir = "/dev"
	scan = [ "/dev" ]
	obtain_device_list_from_udev = 1
	external_device_info_source = "none"
	cache_dir = "/etc/lvm/cache"
	cache_file_prefix = ""
	write_cache_state = 1
	sysfs_scan = 1
	multipath_component_detection = 1
	md_component_detection = 1
	fw_raid_component_detection = 0
	md_chunk_alignment = 1
	data_alignment_detection = 1
	data_alignment = 0
	data_alignment_offset_detection = 1
	ignore_suspended_devices = 0
	ignore_lvm_mirrors = 1
	disable_after_error_count = 0
	require_restorefile_with_uuid = 1
	pv_min_size = 2048
	issue_discards = 0
}
allocation {
	maximise_cling = 1
	use_blkid_wiping = 1
	wipe_signatures_when_zeroing_new_lvs = 1
	mirror_logs_require_separate_pvs = 0
	cache_pool_metadata_require_separate_pvs = 0
	thin_pool_metadata_require_separate_pvs = 0
}
log {
	verbose = 0
	silent = 0
	syslog = 1
	overwrite = 0
	level = 0
	indent = 1
	command_names = 0
	prefix = "  "
	activation = 0
	debug_classes = [ "memory", "devices", "activation", "allocation",
"lvmetad", "metadata", "cache", "locking", "lvmpolld" ]
}
backup {
	backup = 1
	backup_dir = "/etc/lvm/backup"
	archive = 1
	archive_dir = "/etc/lvm/archive"
	retain_min = 10
	retain_days = 30
}
shell {
	history_size = 100
}
global {
	umask = 077
	test = 0
	units = "h"
	si_unit_consistency = 1
	suffix = 1
	activation = 1
	proc = "/proc"
	etc = "/etc"
	locking_type = 1
	wait_for_locks = 1
	fallback_to_clustered_locking = 1
	fallback_to_local_locking = 1
	locking_dir = "/run/lock/lvm"
	prioritise_write_locks = 1
	abort_on_internal_errors = 0
	detect_internal_vg_cache_corruption = 0
	metadata_read_only = 0
	mirror_segtype_default = "raid1"
	raid10_segtype_default = "raid10"
	sparse_segtype_default = "thin"
	use_lvmetad = 1
	use_lvmlockd = 0
	system_id_source = "none"
	use_lvmpolld = 0
}
activation {
	checks = 0
	udev_sync = 1
	udev_rules = 1
	verify_udev_operations = 0
	retry_deactivation = 1
	missing_stripe_filler = "error"
	use_linear_target = 1
	reserved_stack = 64
	reserved_memory = 8192
	process_priority = -18
	raid_region_size = 512
	readahead = "auto"
	raid_fault_policy = "warn"
	mirror_image_fault_policy = "remove"
	mirror_log_fault_policy = "allocate"
	snapshot_autoextend_threshold = 100
	snapshot_autoextend_percent = 20
	thin_pool_autoextend_threshold = 100
	thin_pool_autoextend_percent = 20
	use_mlockall = 0
	monitoring = 1
	polling_interval = 15
	activation_mode = "degraded"
}
dmeventd {
	mirror_library = "libdevmapper-event-lvm2mirror.so"
	snapshot_library = "libdevmapper-event-lvm2snapshot.so"
	thin_library = "libdevmapper-event-lvm2thin.so"
}



> Well, generally, if disk sectors accommodating PV header are damaged,
> lvm2 won't recognise the device...

:(


-- 
http://utopia.partidopirata.com.ar/


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 585 bytes --]

  reply	other threads:[~2016-05-31 13:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-30 21:54 [dm-crypt] LVM on LUKS: volumes missing fauno
2016-05-31  7:53 ` Ondrej Kozina
2016-05-31  7:53   ` [linux-lvm] " Ondrej Kozina
2016-05-31 13:17   ` fauno [this message]
2016-06-02 13:22     ` Ondrej Kozina
2016-06-02 13:39       ` fauno
2016-06-02 13:52         ` fauno
2016-06-02 14:50         ` Zdenek Kabelac
2016-06-02 15:09           ` fauno
2016-06-02 15:20             ` Zdenek Kabelac
2016-05-31 12:52 ` Robert Nichols
2016-05-31 14:54   ` fauno
2016-06-02 12:57     ` fauno
2016-06-02 18:31       ` Robert Nichols
2016-06-03 21:42       ` Arno Wagner
2016-06-03 22:46         ` Robert Nichols
2016-06-04  8:06           ` Arno Wagner
2016-06-07 14:24             ` fauno

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=574D8EE6.8020903@partidopirata.com.ar \
    --to=fauno@partidopirata.com.ar \
    --cc=linux-lvm@redhat.com \
    --cc=okozina@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.