Re: [linux-lvm] lvm2 raid volumes
Heinz Mauelshagen schreef op 16-09-2016 16:13: Yes, looks like you don't have the 2nd PV accessible by the time when the raid1 is being discovered and initially activated, hence the superblock can't be retrieved. These messages seem to be coming from initramfs, so check which driver is missing/not loaded to access the 2nd PV. The fact that you gain access to the raid1 completely after reboot (as you mention further down) tells the aforementioned fact is reasoning this degraded activation. I.e. disk driver loaded after root pivot. Please ensure it is available in the initramfs and loaded. Heinz Yes, thank you. The problem was that the VG that contained the PV used as the 2nd PV was not getting activated at initramfs time. I solved it now by creating some hooks that would obtain a hierarchical PV list from a running system and then ensure all PVs in that list that were also LVs, would get activated prior to the root device. The issue is really that (on Ubuntu) LV activation is very selective in the initramfs. Of course it is an embedded or "enclosed" setup, maybe it is not recommended. Regardless the only issue was that LVs are getting selectively activated (only root and swap). Regards. ___ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
Re: [linux-lvm] lvm2 raid volumes
On 08/15/2016 03:38 PM, Xen wrote: Heinz Mauelshagen schreef op 03-08-2016 15:10: The Cyp%Sync field tells you about the resynchronization progress, i.e. the initial mirroring of all data blocks in a raid1/10 or the initial calculation and storing of parity blocks in raid4/5/6. Heinz, can I perhaps ask you here. If I can. I have put a root volume on raid 1. Maybe "of course" the second disk (LVM volumes) are not available at system boot: aug 15 14:09:19 xenpc2 kernel: device-mapper: raid: Loading target version 1.7.0 aug 15 14:09:19 xenpc2 kernel: device-mapper: raid: Failed to read superblock of device at position 1 Yes, looks like you don't have the 2nd PV accessible by the time when the raid1 is being discovered and initially activated, hence the superblock can't be retrieved. These messages seem to be coming from initramfs, so check which driver is missing/not loaded to access the 2nd PV. The fact that you gain access to the raid1 completely after reboot (as you mention further down) tells the aforementioned fact is reasoning this degraded activation. I.e. disk driver loaded after root pivot. Please ensure it is available in the initramfs and loaded. Heinz aug 15 14:09:19 xenpc2 kernel: md/raid1:mdX: active with 1 out of 2 mirrors aug 15 14:09:19 xenpc2 kernel: created bitmap (15 pages) for device mdX aug 15 14:09:19 xenpc2 kernel: mdX: bitmap initialized from disk: read 1 pages, set 19642 of 30040 bits aug 15 14:09:19 xenpc2 kernel: EXT4-fs (dm-6): mounted filesystem with ordered data mode. Opts: (null) This could be because I am using PV directly on disk (no partition table) for *some* volumes (actually the first disk, that is booted from), however, I force a start of LVM2 service by enabling it in SystemD: aug 15 14:09:19 xenpc2 systemd[1]: Starting LVM2... This is further down the log, so LVM is actually started after the RAID is loading. At that point normally, from my experience, only the root LV is available. Then at a certain point more devices become available: aug 15 14:09:22 xenpc2 systemd[1]: Found device /dev/mapper/msata-boot. aug 15 14:09:22 xenpc2 systemd[1]: Started LVM2. aug 15 14:09:22 xenpc2 systemd[1]: Found device /dev/raid/tmp. aug 15 14:09:22 xenpc2 systemd[1]: Found device /dev/raid/swap. aug 15 14:09:22 xenpc2 systemd[1]: Found device /dev/raid/var. But just before that happens, there are some more RAID1 errors: aug 15 14:09:22 xenpc2 kernel: device-mapper: raid: Failed to read superblock of device at position 1 aug 15 14:09:22 xenpc2 kernel: md/raid1:mdX: active with 1 out of 2 mirrors aug 15 14:09:22 xenpc2 kernel: created bitmap (1 pages) for device mdX aug 15 14:09:22 xenpc2 kernel: mdX: bitmap initialized from disk: read 1 pages, set 320 of 480 bits aug 15 14:09:22 xenpc2 kernel: device-mapper: raid: Failed to read superblock of device at position 1 aug 15 14:09:22 xenpc2 kernel: md/raid1:mdX: active with 1 out of 2 mirrors aug 15 14:09:22 xenpc2 kernel: created bitmap (15 pages) for device mdX aug 15 14:09:22 xenpc2 kernel: mdX: bitmap initialized from disk: read 1 pages, set 19642 of 30040 bits Well small wonder if the device isn't there yet. There are no messages for it, but I will assume the mirror LVs came online at the same time as the other "raid" volume group LVs, which means the RAID errors preceded that. Hence, no secondary mirror volumes available, cannot start the raid, right. However after logging in, the Cpy%Sync behaviour seems normal: boot msata rwi-aor--- 240,00m100,00 root msata rwi-aor--- 14,67g 100,00 Devices are shown as: boot msata rwi-aor--- 240,00m 100,00 boot_rimage_0(0),boot_rimage_1(0) root msata rwi-aor--- 14,67g 100,00 root_rimage_0(0),root_rimage_1(0) dmsetup table seems normal: # dmsetup table | grep msata | sort coll-msata--lv: 0 60620800 linear 8:36 2048 msata-boot: 0 491520 raid raid1 3 0 region_size 1024 2 252:14 252:15 - - msata-boot_rimage_0: 0 491520 linear 8:16 4096 msata-boot_rimage_1: 0 491520 linear 252:12 10240 msata-boot_rimage_1-missing_0_0: 0 491520 error msata-boot_rmeta_0: 0 8192 linear 8:16 495616 msata-boot_rmeta_1: 0 8192 linear 252:12 2048 msata-boot_rmeta_1-missing_0_0: 0 8192 error msata-root: 0 30760960 raid raid1 3 0 region_size 1024 2 252:0 252:1 - - msata-root_rimage_0: 0 30760960 linear 8:16 512000 msata-root_rimage_1: 0 30760960 linear 252:12 509952 msata-root_rimage_1-missing_0_0: 0 30760960 error msata-root_rmeta_0: 0 8192 linear 8:16 503808 msata-root_rmeta_1: 0 8192 linear 252:12 501760 msata-root_rmeta_1-missing_0_0: 0 8192 error But actually it's not because it should reference 4 devices, not two. Apologies. It only references the volumes of the first disk (image and meta). E.g. 252:0 and 252:1 are: lrwxrwxrwx 1 root root 7 aug 15 14:09 msata-root_rmeta_0 -> ../dm-0 lrwxrwxrwx 1 root root 7 aug 15 14:09
Re: [linux-lvm] lvm2 raid volumes
Heinz Mauelshagen schreef op 03-08-2016 15:10: The Cyp%Sync field tells you about the resynchronization progress, i.e. the initial mirroring of all data blocks in a raid1/10 or the initial calculation and storing of parity blocks in raid4/5/6. Heinz, can I perhaps ask you here. If I can. I have put a root volume on raid 1. Maybe "of course" the second disk (LVM volumes) are not available at system boot: aug 15 14:09:19 xenpc2 kernel: device-mapper: raid: Loading target version 1.7.0 aug 15 14:09:19 xenpc2 kernel: device-mapper: raid: Failed to read superblock of device at position 1 aug 15 14:09:19 xenpc2 kernel: md/raid1:mdX: active with 1 out of 2 mirrors aug 15 14:09:19 xenpc2 kernel: created bitmap (15 pages) for device mdX aug 15 14:09:19 xenpc2 kernel: mdX: bitmap initialized from disk: read 1 pages, set 19642 of 30040 bits aug 15 14:09:19 xenpc2 kernel: EXT4-fs (dm-6): mounted filesystem with ordered data mode. Opts: (null) This could be because I am using PV directly on disk (no partition table) for *some* volumes (actually the first disk, that is booted from), however, I force a start of LVM2 service by enabling it in SystemD: aug 15 14:09:19 xenpc2 systemd[1]: Starting LVM2... This is further down the log, so LVM is actually started after the RAID is loading. At that point normally, from my experience, only the root LV is available. Then at a certain point more devices become available: aug 15 14:09:22 xenpc2 systemd[1]: Found device /dev/mapper/msata-boot. aug 15 14:09:22 xenpc2 systemd[1]: Started LVM2. aug 15 14:09:22 xenpc2 systemd[1]: Found device /dev/raid/tmp. aug 15 14:09:22 xenpc2 systemd[1]: Found device /dev/raid/swap. aug 15 14:09:22 xenpc2 systemd[1]: Found device /dev/raid/var. But just before that happens, there are some more RAID1 errors: aug 15 14:09:22 xenpc2 kernel: device-mapper: raid: Failed to read superblock of device at position 1 aug 15 14:09:22 xenpc2 kernel: md/raid1:mdX: active with 1 out of 2 mirrors aug 15 14:09:22 xenpc2 kernel: created bitmap (1 pages) for device mdX aug 15 14:09:22 xenpc2 kernel: mdX: bitmap initialized from disk: read 1 pages, set 320 of 480 bits aug 15 14:09:22 xenpc2 kernel: device-mapper: raid: Failed to read superblock of device at position 1 aug 15 14:09:22 xenpc2 kernel: md/raid1:mdX: active with 1 out of 2 mirrors aug 15 14:09:22 xenpc2 kernel: created bitmap (15 pages) for device mdX aug 15 14:09:22 xenpc2 kernel: mdX: bitmap initialized from disk: read 1 pages, set 19642 of 30040 bits Well small wonder if the device isn't there yet. There are no messages for it, but I will assume the mirror LVs came online at the same time as the other "raid" volume group LVs, which means the RAID errors preceded that. Hence, no secondary mirror volumes available, cannot start the raid, right. However after logging in, the Cpy%Sync behaviour seems normal: boot msata rwi-aor--- 240,00m 100,00 root msata rwi-aor--- 14,67g 100,00 Devices are shown as: boot msata rwi-aor--- 240,00m 100,00 boot_rimage_0(0),boot_rimage_1(0) root msata rwi-aor--- 14,67g 100,00 root_rimage_0(0),root_rimage_1(0) dmsetup table seems normal: # dmsetup table | grep msata | sort coll-msata--lv: 0 60620800 linear 8:36 2048 msata-boot: 0 491520 raid raid1 3 0 region_size 1024 2 252:14 252:15 - - msata-boot_rimage_0: 0 491520 linear 8:16 4096 msata-boot_rimage_1: 0 491520 linear 252:12 10240 msata-boot_rimage_1-missing_0_0: 0 491520 error msata-boot_rmeta_0: 0 8192 linear 8:16 495616 msata-boot_rmeta_1: 0 8192 linear 252:12 2048 msata-boot_rmeta_1-missing_0_0: 0 8192 error msata-root: 0 30760960 raid raid1 3 0 region_size 1024 2 252:0 252:1 - - msata-root_rimage_0: 0 30760960 linear 8:16 512000 msata-root_rimage_1: 0 30760960 linear 252:12 509952 msata-root_rimage_1-missing_0_0: 0 30760960 error msata-root_rmeta_0: 0 8192 linear 8:16 503808 msata-root_rmeta_1: 0 8192 linear 252:12 501760 msata-root_rmeta_1-missing_0_0: 0 8192 error But actually it's not because it should reference 4 devices, not two. Apologies. It only references the volumes of the first disk (image and meta). E.g. 252:0 and 252:1 are: lrwxrwxrwx 1 root root 7 aug 15 14:09 msata-root_rmeta_0 -> ../dm-0 lrwxrwxrwx 1 root root 7 aug 15 14:09 msata-root_rimage_0 -> ../dm-1 Whereas the volumes from the other disk are: lrwxrwxrwx 1 root root 7 aug 15 14:09 msata-root_rmeta_1 -> ../dm-3 lrwxrwxrwx 1 root root 7 aug 15 14:09 msata-root_rimage_1 -> ../dm-5 If I dismount /boot, lvchange -an msata/boot, lvchange -ay msata/boot, it loads correctly: aug 15 14:56:23 xenpc2 kernel: md/raid1:mdX: active with 1 out of 2 mirrors aug 15 14:56:23 xenpc2 kernel: created bitmap (1 pages) for device mdX aug 15 14:56:23 xenpc2 kernel: mdX: bitmap initialized
