Re: [gentoo-user] systemd mount - what on earth is it doing ...

[Canek Peláez Valdés]

On Fri, Sep 24, 2021 at 2:25 PM antlists <antlists@××××××××××××.uk> wrote:

> This is weird ...
>
> My /home directory is set up somewhat strangely, as in I've got two raw
> partitions, I've put dm-integrity on them, raided them together, then
> put lvm on top of that.
>

> Which got me into a bind with fstab. I've created a systemd service,
> which fires up dm-integrity on those two partitions. But I get the
> impression it doesn't run until fstab completes. Catch-22 - fstab tries
> to mount /home, but it can't until dm-integrity has made the volume appear!
>

Have you tried using Before=local-fs.target in the service? Or even
Before=local-fs-pre.target?

So I created a systemd mount unit for /home, which only runs after
> dm-integrity. Great - I enabled it and it appeared to work!
>

You removed the /home entry from fstab, right?


> Only problem, startplasma-wayland now dumped me at a blank screen.
>
> Now for the weirdo. I disabled it, thinking I would have to log in as
> root, mount /home, and go from there. Except that, when I logged in,
> /home was mounted and startplasma-wayland worked!
>

That sounds like /home was still on fstab...


> systemctl tells me mount.home is disabled, but also tells me that it ran
> and mounted the drive.
>

That should be home.mount. What does systemctl status home.mount says?


> So what on earth is going on, and more importantly, what am I
> misunderstanding or doing wrong. I would very much like to know why it's
> working, when I think it shouldn't be!
>

Regards.
-- 
Dr. Canek Peláez Valdés
Profesor de Carrera Asociado C
Departamento de Matemáticas
Facultad de Ciencias
Universidad Nacional Autónoma de México