archive mirror
 help / color / mirror / Atom feed
From: pasxizeis <>
Subject: [linux-lvm] Q: lvcreate, systemd and tmp.mount
Date: Mon, 23 Mar 2020 20:03:27 +0200	[thread overview]
Message-ID: <> (raw)

[-- Attachment #1: Type: text/plain, Size: 1716 bytes --]

Hi all,

Perhaps this is more of a systemd-related question, but I wasn't sure so 
here I go. I'm running into an issue where an lvcreate invocation 
somehow (supposedly) results in systemd trying to activate tmp.mount.[14099]: foopkg-utils [14099]: INFO RunCmd: lvcreate -kn
    --addtag @bar -s -n

    dmeventd[663]: No longer monitoring thin pool
    storage-thinpool-tpool. lvm[663]: Monitoring thin pool
    storage-thinpool-tpool.[14099]: foopkg-utils [14099]: WARNING Command 'lvcreate
    -kn --addtag @bar -s -n bar_elastic-1582433367seven
    storage/bar_elastic-1582433367' stderr out: ' WARNING: Sum of all
    thin volume sizes (2.98 TiB) exceeds the size of thin pool
    storage/thinpool and the size of whole volume group (378.00 GiB)! '

    systemd[1]: tmp.mount: Directory /tmp to mount over is not empty,
    mounting anyway.

    systemd[1]: tmp.mount: Failed to run 'mount' task: No such file or
    directory systemd[1]: Failed to mount /tmp.

The thing is (a) I don't have tmp.mount activated (my /tmp belongs in 
the root fs) and there is no relevant entry in `/etc/fstab`. The unit is 
only defined at `/usr/share/systemd/tmp.mount`. So I don't get why 
systemd is trying to mount tmp.mount at all and why only after the 
`lvcreate` invocation.

Another interesting observation, is that even though I also do other 
lvcreate invocations from the same group, the tmp.mount issue only comes 
after invocations where the lv name ends with `.seven` (like in my 
example above).

This is Debian Stretch with lvm 2.02.168.

Any ideas?

Thanks in advance!

[-- Attachment #2: Type: text/html, Size: 2189 bytes --]

                 reply	other threads:[~2020-03-23 18:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).