BTRFS on LVM causes long fedora-storage-init run?

Clyde E. Kunkel clydekunkel7734 at
Fri Oct 7 16:17:25 UTC 2011

On 10/07/2011 11:31 AM, Richard Shaw wrote:
> I posted this on the main mailing list but didn't get any hits.
> Hopefully I'll have better luck here.
> ---
> I found the following thread but I don't think mine is the same problem:
> I am, however, running BTRFS on main main partitions on top of LVM
> (since anaconda as of F15 still creates an LVM setup regardless of
> filesystem?)
> This is the only thing I can think of that's causing the problem.
> $ systemd-analyze blame | head
>   47003ms fedora-storage-init.service
>   30284ms boot.mount
>   8829ms udev-settle.service
>   3692ms cups.service
>   1686ms systemd-vconsole-setup.service
>   1567ms udev.service
>   1510ms autofs.service
>   1403ms fedora-readonly.service
>   1311ms lvm2-monitor.service
>   1295ms NetworkManager.service
> boot.mount I assume just remounts the boot partition as read-write, so
> I think it's just waiting on fedora-storage-init.service.
> Any ideas?
> Thanks,
> Richard

Don't really know...but, if no LV snapshots, then suspect BTRFS as it is 
still very experimental.  There is a newer lvm2 
(lvm2-2.02.84-4.fc15.x86_64) which fixed the LVM snapshot problem and 
systemd (systemd-26-10.fc15.x86_64) for F15.


More information about the devel mailing list