[Bug 893450] Re: libvirt fails to start correctly because LVM is not ready
[Expired for udev (Ubuntu) because there has been no activity for 60 days.] ** Changed in: udev (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/893450 Title: libvirt fails to start correctly because LVM is not ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/893450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 893450] Re: libvirt fails to start correctly because LVM is not ready
[Expired for libvirt (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libvirt (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/893450 Title: libvirt fails to start correctly because LVM is not ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/893450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 893450] Re: libvirt fails to start correctly because LVM is not ready
The disk sector size and how it's managed really determine how well it will perform under various access sizes. In your case remember, the disk sector size is 4k, so we would hope that Linux is "doing the right thing" in coalescing these 1k accesses into chunks which get the most out of your hard disks. That's not our primary problem here, the primary problem here is LVM having trouble bringing all LVs online. These performance issues are in addition to that. The LVM problem appears to have been addressed by adding a root delay so that's that. We have yet to pin down where any of them have come from. That this problem appeared after an update is suspicious, yet iirc you've shown that rolling kernels back and forth have no net impact on the symptoms. If an update was really the root of all of this you should be able to install natty to a separate set of disks, re-run these tests and see dramatically different numbers for the 1K test runs. We are now left with the actual configuration of your entire stack, the loads generated by your VMs, and how they might be affecting your IO subsystem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/893450 Title: libvirt fails to start correctly because LVM is not ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/893450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 893450] Re: libvirt fails to start correctly because LVM is not ready
All the tests where ran at the bare metal level. The results on comment 16 where ran over a ext4 over lvm over raid1. The results on comment 17 where ran over a ext4 over a plain partition. I don't know how bad are those numbers... Maybe it's normal that working with 1k blocks kill's the disk performance? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/893450 Title: libvirt fails to start correctly because LVM is not ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/893450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 893450] Re: libvirt fails to start correctly because LVM is not ready
Are these ext4 test results done at the bare metal level or from the guest? With the guests themselves, are they using the raw volume for the image or do they exist as an image file on the filesystem. If they're images files, then what fs type do they live on? Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/893450 Title: libvirt fails to start correctly because LVM is not ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/893450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 893450] Re: libvirt fails to start correctly because LVM is not ready
The same tests, now on a ext4 filesystem over plain partition (no RAID) - Record size 1k Children see throughput for 2 initial writers = 34.09 KB/sec Avg throughput per process = 17.04 KB/sec Children see throughput for 2 rewriters= 25.68 KB/sec Avg throughput per process = 12.84 KB/sec - Record size 8k Children see throughput for 2 initial writers = 195.30 KB/sec Avg throughput per process = 97.65 KB/sec Children see throughput for 2 rewriters= 199.05 KB/sec Avg throughput per process = 99.52 KB/sec - Record size 128k Children see throughput for 2 initial writers =3248.37 KB/sec Avg throughput per process =1624.19 KB/sec Children see throughput for 2 rewriters=3197.46 KB/sec Avg throughput per process =1598.73 KB/sec -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/893450 Title: libvirt fails to start correctly because LVM is not ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/893450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 893450] Re: libvirt fails to start correctly because LVM is not ready
And some iozone tests, with 2 child process, O_DIRECT and SYNC Mode (full log on pastebin: http://pastebin.com/amTbjfdr). All with: O_DIRECT feature enabled SYNC Mode. Output is in Kbytes/sec Min process = 2 Max process = 2 Throughput test with 2 processes - Record size 1k Children see throughput for 2 initial writers = 11.50 KB/sec Avg throughput per process = 5.75 KB/sec Children see throughput for 2 rewriters= 12.45 KB/sec Avg throughput per process = 6.22 KB/sec - Record size 8k Children see throughput for 2 initial writers = 100.18 KB/sec Avg throughput per process = 50.09 KB/sec Children see throughput for 2 rewriters= 75.27 KB/sec Avg throughput per process = 37.64 KB/sec - Record size 16k Children see throughput for 2 initial writers = 277.43 KB/sec Avg throughput per process = 138.71 KB/sec Children see throughput for 2 rewriters= 224.98 KB/sec Avg throughput per process = 112.49 KB/sec - Record size 32k Children see throughput for 2 initial writers = 398.72 KB/sec Avg throughput per process = 199.36 KB/sec Children see throughput for 2 rewriters= 204.58 KB/sec Avg throughput per process = 102.29 KB/sec - Record size 64k Children see throughput for 2 initial writers = 406.26 KB/sec Avg throughput per process = 203.13 KB/sec Children see throughput for 2 rewriters= 447.78 KB/sec Avg throughput per process = 223.89 KB/sec - Record size 128k Children see throughput for 2 initial writers =1711.68 KB/sec Avg throughput per process = 855.84 KB/sec Children see throughput for 2 rewriters=1563.11 KB/sec Avg throughput per process = 781.56 KB/sec - Record size 256k Children see throughput for 2 initial writers =3400.94 KB/sec Avg throughput per process =1700.47 KB/sec Children see throughput for 2 rewriters=2532.04 KB/sec Avg throughput per process =1266.02 KB/sec -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/893450 Title: libvirt fails to start correctly because LVM is not ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/893450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 893450] Re: libvirt fails to start correctly because LVM is not ready
Some comments about performance: - reading works well with big and small block sizes - writing with big block size works ok - the problem arise when writing with small block size -- Reading works ok with small and large block size: reading blocks of 1KiB from sda2 # /usr/bin/time dd if=/dev/sda2 of=/dev/null bs=1024 count=$(( 1024*32 )) 32768+0 records in 32768+0 records out 33554432 bytes (34 MB) copied, 0.48956 s, 68.5 MB/s 0.00user 0.07system 0:00.49elapsed 14%CPU (0avgtext+0avgdata 3552maxresident)k 66016inputs+0outputs (0major+268minor)pagefaults 0swaps # /usr/bin/time dd if=/dev/sda2 of=/dev/null bs=1024 count=$(( 1024*1024 )) 1048576+0 records in 1048576+0 records out 1073741824 bytes (1.1 GB) copied, 8.74106 s, 123 MB/s 0.08user 2.23system 0:08.74elapsed 26%CPU (0avgtext+0avgdata 3536maxresident)k 2097632inputs+0outputs (0major+268minor)pagefaults 0swaps reading blocks of 1MiB from sdb2 (to ensure that nothing is cached) # /usr/bin/time dd if=/dev/sdb2 of=/dev/null bs=$((1024*1024)) count=1024 1024+0 records in 1024+0 records out 1073741824 bytes (1.1 GB) copied, 8.76866 s, 122 MB/s 0.00user 1.82system 0:08.77elapsed 20%CPU (0avgtext+0avgdata 7616maxresident)k 2097408inputs+0outputs (0major+522minor)pagefaults 0swaps Now, writing with blocks of 16MiB works ok (64.5 MB/s!!!) # /usr/bin/time dd if=/dev/zero of=/mnt/rsync/zeros bs=$((1024*1024*16)) count=128 oflag=dsync 128+0 records in 128+0 records out 2147483648 bytes (2.1 GB) copied, 33.2825 s, 64.5 MB/s 0.00user 6.69system 0:33.37elapsed 20%CPU (0avgtext+0avgdata 69072maxresident)k 1464inputs+4195328outputs (0major+4363minor)pagefaults 0swaps With 1MiB the performance is bad (12.1 MB/s) # /usr/bin/time dd if=/dev/zero of=/mnt/rsync/zeros bs=$((1024*1024)) count=256 oflag=dsync 256+0 records in 256+0 records out 268435456 bytes (268 MB) copied, 22.1709 s, 12.1 MB/s 0.00user 0.97system 0:22.17elapsed 4%CPU (0avgtext+0avgdata 7616maxresident)k 40inputs+524288outputs (1major+521minor)pagefaults 0swaps With 1KiB I got.. 33.3 kB/s!!! (I pressed Ctrl+C after some time) # /usr/bin/time dd if=/dev/zero of=/mnt/rsync/zeros bs=1024 count=$(( 1024*32 )) oflag=dsync (pressed Ctrl+C) ^C9069+0 records in 9069+0 records out 9286656 bytes (9.3 MB) copied, 279.276 s, 33.3 kB/s Command terminated by signal 2 0.00user 1.30system 4:39.90elapsed 0%CPU (0avgtext+0avgdata 3504maxresident)k 0inputs+72552outputs (0major+265minor)pagefaults 0swaps -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/893450 Title: libvirt fails to start correctly because LVM is not ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/893450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 893450] Re: libvirt fails to start correctly because LVM is not ready
I've made more test with the guidance of Peter Petrakis, I've physically removed the LSI card and tryied with a newer kernel (3.0.0-15) without luck... the performance is the same (read ok, but slow writes). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/893450 Title: libvirt fails to start correctly because LVM is not ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/893450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 893450] Re: libvirt fails to start correctly because LVM is not ready
Worked with the user on irc and ruled out screaming interrupts and the LSI card itself (he removed it). User is upgrading to 3.x kernel and will apprise us of his progress here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/893450 Title: libvirt fails to start correctly because LVM is not ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/893450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 893450] Re: libvirt fails to start correctly because LVM is not ready
Ok, I've added seagate disks, manually created partitions (aligned to
1mb), added the new discs to the raid, remove the wd discs. The raid is
now over two seagate disks, and the performance is still crap.
# hdparm -i /dev/sda
Model=ST2000DL003-9VT166, FwRev=CC32, SerialNo=6YD0RYED
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=unknown, BuffSize=unknown, MaxMultSect=16, MultSect=16
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=3907029168
I've tryied to make the partition aligned to 1mb, maybe I made the
partitions wrong.. These are the partitions on /dev/sda:
# sfdisk -s -d /dev/sda
1953514584
# partition table of /dev/sda
unit: sectors
/dev/sda1 : start= 2048, size= 19531776, Id=fd
/dev/sda2 : start= 19533824, size= 9762816, Id=83
/dev/sda3 : start= 29296640, size=3877730304, Id=fd
/dev/sda4 : start=0, size=0, Id= 0
Please, tell me if the partitions aren't aligned. I think I done this
right, multiples of 2048 (1mb).
If the partitions are right, the problem aren't the disks, neither raid,
lvm nor the fs, since I've tested with dd over /dev/sda2 (plain
partition, no raid, no lvm, no filesystem):
# dd if=/dev/zero of=/dev/sda2 count=1000 oflag=dsync bs=16384
16384000 bytes (16 MB) copied, 12.5848 s, 1.3 MB/s
# dd if=/dev/zero of=/dev/sda2 count=1000 oflag=dsync bs=16384
16384000 bytes (16 MB) copied, 14.4387 s, 1.1 MB/s
With raid, lvm and ext4, the performance is:
# dd if=/dev/zero of=zeros count=1000 oflag=dsync bs=512
512000 bytes (512 kB) copied, 19.4532 s, 26.3 kB/s
# dd if=/dev/zero of=zeros count=1000 oflag=dsync bs=1024
1024000 bytes (1.0 MB) copied, 22.373 s, 45.8 kB/s
# dd if=/dev/zero of=zeros count=1000 oflag=dsync bs=2048
2048000 bytes (2.0 MB) copied, 28.7906 s, 71.1 kB/s
# dd if=/dev/zero of=zeros count=1000 oflag=dsync bs=4096
4096000 bytes (4.1 MB) copied, 68.0617 s, 60.2 kB/s
# dd if=/dev/zero of=zeros count=1000 oflag=dsync bs=8192
8192000 bytes (8.2 MB) copied, 61.7608 s, 133 kB/s
# dd if=/dev/zero of=zeros count=1000 oflag=dsync bs=16384
16384000 bytes (16 MB) copied, 67.1279 s, 244 kB/s
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/893450
Title:
libvirt fails to start correctly because LVM is not ready
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/893450/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 893450] Re: libvirt fails to start correctly because LVM is not ready
** Changed in: libvirt (Ubuntu) Status: New => Incomplete ** Changed in: udev (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/893450 Title: libvirt fails to start correctly because LVM is not ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/893450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 893450] Re: libvirt fails to start correctly because LVM is not ready
In re-examining the evidence and chatting with Serge a few things come to mind. 1) There's a disparity between the conclusion formed in comment #3 and the latest udev logs. It could easily be true that the udev logging simply was held long enough for that last LV to be activated. It appears to be true that if we wait long enough (approx 10 mins) that all LVs will come online. 2) The crux is udev being starved of events or is it being stalled by some other action? 3) Comment #9 compelled me to dig around concerning the backing store's to the RAID 1 software set. The WD20EARS appear to use 4K sectors, which if true would lend credence to *slowness* being the factor (udev is starved) which determines why it takes almost 10 mins to discover all the LVs. Follow up: 1) verify sector size of backing stores by installing sg3-utils and posting the result of # sg_readcap /dev/sda and # cat /sys/block/sda/queue/physical_block_size 2) the basic dd test is fine, please re-run with a sweep of blocksizes, 512, 4k, 8k, 1024k with "count=100" so it doesn't run forever 3) an additional io benchmark would be informative like iozone or iometer, whatever is your preference. Conclusion: If this is an alignment issue then we've got a lot of work to do. You might be able to resize/grow the MD array to change the stripe size to be a multiple of the sector size. Though you would need to carry the exercise all the way through, including LVM metadata offsets. It would be optimal if you had a duplicate set of drives to reproduce this issue on a separate system. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/893450 Title: libvirt fails to start correctly because LVM is not ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/893450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 893450] Re: libvirt fails to start correctly because LVM is not ready
Sure enough, lv_robot-pv0 (the backing lv for the vm) doesn't show up either in the lvscan or udev debug output. Certainly a lvm failure here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/893450 Title: libvirt fails to start correctly because LVM is not ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/893450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 893450] Re: libvirt fails to start correctly because LVM is not ready
** Changed in: libvirt (Ubuntu) Status: Incomplete => New ** Changed in: udev (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/893450 Title: libvirt fails to start correctly because LVM is not ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/893450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 893450] Re: libvirt fails to start correctly because LVM is not ready
I've attached /dev/.initramfs/udev.out. I don'n know if this is
relevant, but the write performance on the disks is horrible, I think
this could be caused by mis-aligment of partitions ("dd if=/dev/zero
of=zeros bs=64b oflag=dsync" gives me around 400kB/s)
** Attachment added: "Contents of /dev/.initramfs/udev.out"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/893450/+attachment/2642972/+files/udev.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/893450
Title:
libvirt fails to start correctly because LVM is not ready
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/893450/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 893450] Re: libvirt fails to start correctly because LVM is not ready
This is the output of the lvm scan commands. I'll ask permission to reboot the server tonight to post the debug output of udev. web4:~# sudo pvscan PV /dev/md1 VG vg_default lvm2 [1.81 TiB / 1.33 TiB free] Total: 1 [1.81 TiB] / in use: 1 [1.81 TiB] / in no VG: 0 [0 ] web4:~# sudo vgscan Reading all physical volumes. This may take a while... Found volume group "vg_default" using metadata type lvm2 web4:~# sudo lvscan ACTIVE'/dev/vg_default/lv_desa_web_2-root' [5.00 GiB] inherit ACTIVE'/dev/vg_default/lv_desa_web_2-swap' [1.00 GiB] inherit ACTIVE'/dev/vg_default/lv_desa_web_2-pv0' [150.00 GiB] inherit ACTIVE'/dev/vg_default/lv_rsync' [200.00 GiB] inherit ACTIVE'/dev/vg_default/lv_cms2-pv0' [10.00 GiB] inherit ACTIVE'/dev/vg_default/lv_cms2-root' [4.00 GiB] inherit ACTIVE'/dev/vg_default/lv_jaime-root' [5.00 GiB] inherit ACTIVE'/dev/vg_default/lv_jaime-pv0' [10.00 GiB] inherit ACTIVE'/dev/vg_default/lv_monitor-swap' [1.00 GiB] inherit ACTIVE'/dev/vg_default/lv_monitor-root' [5.00 GiB] inherit ACTIVE'/dev/vg_default/lv_monitor-pv0' [50.00 GiB] inherit ACTIVE'/dev/vg_default/lv_monitor-var' [47.00 GiB] inherit -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/893450 Title: libvirt fails to start correctly because LVM is not ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/893450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 893450] Re: libvirt fails to start correctly because LVM is not ready
Please don't change the state from incomplete until the requested information has been provided. ** Changed in: udev (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/893450 Title: libvirt fails to start correctly because LVM is not ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/893450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 893450] Re: libvirt fails to start correctly because LVM is not ready
** Changed in: udev (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/893450 Title: libvirt fails to start correctly because LVM is not ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/893450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 893450] Re: libvirt fails to start correctly because LVM is not ready
Hi, to find out more, we need the udev debug output. Could you please edit /usr/share/initramfs-tools/scripts/init-top/udev so that the line starting udevd reads: /sbin/udevd --daemon --debug --resolve-names=never > /dev/.initramfs/udev.out 2>&1 then run sudo update-initramfs -k all -u After a reboot, you'll find the debug info in /dev/.initramfs/udev.out. Please attach that here. Please also give us the output of the commands: sudo pvscan sudo vgscan sudo lvscan ** Changed in: udev (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/893450 Title: libvirt fails to start correctly because LVM is not ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/893450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 893450] Re: libvirt fails to start correctly because LVM is not ready
** Summary changed: - KVM guest fails to autostart sometimes with virSecurityDACRestoreSecurityFileLabel error + libvirt fails to start correctly because LVM is not ready -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/893450 Title: libvirt fails to start correctly because LVM is not ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/893450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
