Re: [systemd-devel] systemd-222 mount issues on CentOS 7

2016-10-05 Thread Andrei Borzenkov 
On Wed, Oct 5, 2016 at 3:08 PM, Lokesh Mandvekar  wrote:
> On Wed, Oct 05, 2016 at 09:38:18AM +0300, Andrei Borzenkov wrote:
>> On Wed, Oct 5, 2016 at 8:24 AM, Lokesh Mandvekar  
>> wrote:
>> > On Tue, Oct 04, 2016 at 10:28:25AM +0200, Michal Sekletar wrote:
>> >> On Tue, Sep 27, 2016 at 5:05 PM, Lokesh Mandvekar
>> >>  wrote:
>> >> > Now, I can mount these partitions with:
>> >> >
>> >> > # lvm vgchange -ay
>> >> >
>> >> > but this still doesn't automount succesfully on a reboot.
>> >> >
>> >> > Did I miss something here?
>> >>
>> >> I'd check from emergency shell whether lvm2-pvscan@.service was run.
>> >> This instantiated systemd service is responsible for scaning LVM PVs
>> >> and auto-activating LVs on them. Note that it is spawned from udev
>> >> rules in case when certain conditions are met, e.g. block device is
>> >> identified as LVM2_member and udev event doesn't have SYSTEMD_READY=0
>> >> property set.
>> >
>> > Michal, thanks for the reply.
>> >
>> > What's the correct way to check if lvm2-pvscan@.service was run?
>> >
>> > I tried:
>> >
>> > # systemctl status lvm2-pvscan@.service
>> > Failed to get properties: Unit name lvm2-pvscan@.service is not valid.
>> >
>>
>> You need to look for instances of template, not for template itself.
>> Unfortunately, the only way to do it is really
>>
>> systemctl --all | grep lvm2-pvscan
>
> Thanks Andrei, I tried this and it returns nothing on my machine.
> Guess it means none of the instances were run?
>

No, it just means no instance is currently active. This is more or
less normal for oneshot units without RemainAfterExit=true flag. So
you need to check journal whether any instance of this template has
been started.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] systemd-222 mount issues on CentOS 7

2016-10-05 Thread Lokesh Mandvekar 
On Wed, Oct 05, 2016 at 09:38:18AM +0300, Andrei Borzenkov wrote:
> On Wed, Oct 5, 2016 at 8:24 AM, Lokesh Mandvekar  
> wrote:
> > On Tue, Oct 04, 2016 at 10:28:25AM +0200, Michal Sekletar wrote:
> >> On Tue, Sep 27, 2016 at 5:05 PM, Lokesh Mandvekar
> >>  wrote:
> >> > Now, I can mount these partitions with:
> >> >
> >> > # lvm vgchange -ay
> >> >
> >> > but this still doesn't automount succesfully on a reboot.
> >> >
> >> > Did I miss something here?
> >>
> >> I'd check from emergency shell whether lvm2-pvscan@.service was run.
> >> This instantiated systemd service is responsible for scaning LVM PVs
> >> and auto-activating LVs on them. Note that it is spawned from udev
> >> rules in case when certain conditions are met, e.g. block device is
> >> identified as LVM2_member and udev event doesn't have SYSTEMD_READY=0
> >> property set.
> >
> > Michal, thanks for the reply.
> >
> > What's the correct way to check if lvm2-pvscan@.service was run?
> >
> > I tried:
> >
> > # systemctl status lvm2-pvscan@.service
> > Failed to get properties: Unit name lvm2-pvscan@.service is not valid.
> >
> 
> You need to look for instances of template, not for template itself.
> Unfortunately, the only way to do it is really
> 
> systemctl --all | grep lvm2-pvscan

Thanks Andrei, I tried this and it returns nothing on my machine.
Guess it means none of the instances were run?

> 
> and then check each individual service.
> 
> Extending systemctl to automatically handle (at least, for display
> purposes) template instances may be useful.


-- 
Lokesh
Freenode: lsm5
GPG: 0xC7C3A0DD
https://keybase.io/lsm5


signature.asc
Description: PGP signature
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] systemd-222 mount issues on CentOS 7

2016-10-05 Thread Andrei Borzenkov 
On Wed, Oct 5, 2016 at 8:24 AM, Lokesh Mandvekar  wrote:
> On Tue, Oct 04, 2016 at 10:28:25AM +0200, Michal Sekletar wrote:
>> On Tue, Sep 27, 2016 at 5:05 PM, Lokesh Mandvekar
>>  wrote:
>> > Now, I can mount these partitions with:
>> >
>> > # lvm vgchange -ay
>> >
>> > but this still doesn't automount succesfully on a reboot.
>> >
>> > Did I miss something here?
>>
>> I'd check from emergency shell whether lvm2-pvscan@.service was run.
>> This instantiated systemd service is responsible for scaning LVM PVs
>> and auto-activating LVs on them. Note that it is spawned from udev
>> rules in case when certain conditions are met, e.g. block device is
>> identified as LVM2_member and udev event doesn't have SYSTEMD_READY=0
>> property set.
>
> Michal, thanks for the reply.
>
> What's the correct way to check if lvm2-pvscan@.service was run?
>
> I tried:
>
> # systemctl status lvm2-pvscan@.service
> Failed to get properties: Unit name lvm2-pvscan@.service is not valid.
>

You need to look for instances of template, not for template itself.
Unfortunately, the only way to do it is really

systemctl --all | grep lvm2-pvscan

and then check each individual service.

Extending systemctl to automatically handle (at least, for display
purposes) template instances may be useful.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] systemd-222 mount issues on CentOS 7

2016-10-04 Thread Lokesh Mandvekar 
On Tue, Oct 04, 2016 at 10:28:25AM +0200, Michal Sekletar wrote:
> On Tue, Sep 27, 2016 at 5:05 PM, Lokesh Mandvekar
>  wrote:
> > Now, I can mount these partitions with:
> >
> > # lvm vgchange -ay
> >
> > but this still doesn't automount succesfully on a reboot.
> >
> > Did I miss something here?
> 
> I'd check from emergency shell whether lvm2-pvscan@.service was run.
> This instantiated systemd service is responsible for scaning LVM PVs
> and auto-activating LVs on them. Note that it is spawned from udev
> rules in case when certain conditions are met, e.g. block device is
> identified as LVM2_member and udev event doesn't have SYSTEMD_READY=0
> property set.

Michal, thanks for the reply.

What's the correct way to check if lvm2-pvscan@.service was run?

I tried:

# systemctl status lvm2-pvscan@.service
Failed to get properties: Unit name lvm2-pvscan@.service is not valid.

> 
> Also, there has been couple of bugfixes since systemd-222 that are
> maybe related. We backported them to RHEL/CentOS 7 (systemd-219).

Could you please link me to these patches if that's doable?
I see the rpm source contains tons of patches.

Thanks,
-- 
Lokesh
Freenode: lsm5
GPG: 0xC7C3A0DD
https://keybase.io/lsm5


signature.asc
Description: PGP signature
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] systemd-222 mount issues on CentOS 7

2016-10-04 Thread Michal Sekletar 
On Tue, Sep 27, 2016 at 5:05 PM, Lokesh Mandvekar
 wrote:
> Now, I can mount these partitions with:
>
> # lvm vgchange -ay
>
> but this still doesn't automount succesfully on a reboot.
>
> Did I miss something here?

I'd check from emergency shell whether lvm2-pvscan@.service was run.
This instantiated systemd service is responsible for scaning LVM PVs
and auto-activating LVs on them. Note that it is spawned from udev
rules in case when certain conditions are met, e.g. block device is
identified as LVM2_member and udev event doesn't have SYSTEMD_READY=0
property set.

Also, there has been couple of bugfixes since systemd-222 that are
maybe related. We backported them to RHEL/CentOS 7 (systemd-219).

Michal
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel