From: Goffredo Baroncelli <kreijack@inwind.it>
To: Dave T <davestechshop@gmail.com>
Cc: devel@roosoft.ltd.uk,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
Phillip Susi <phill@thesusis.net>,
kilobyte@angband.pl
Subject: Re: why is the same mount point repeatedly mounted in nested manner?
Date: Tue, 10 Aug 2021 17:43:33 +0200 [thread overview]
Message-ID: <2074ef97-dbc2-d588-3000-622ffcf7e062@inwind.it> (raw)
In-Reply-To: <CAGdWbB7KOzsWUEJWtKDfTD-hXOeh+Rhvk1iuXeRMjdqxVhA_uw@mail.gmail.com>
On 8/9/21 10:15 PM, Dave T wrote:
> On Mon, Aug 9, 2021 at 3:29 PM Goffredo Baroncelli <kreijack@libero.it> wrote:
>>
[...]
>
> Also, in recent days I stopped mounting and umounting /mnt/btrtop/root
> and just left it mounted all the time. However, when checking today, I
> still found a nested mount:
>
> ├─/srv/nfs/var/cache/pacman
> │
> │ └─/srv/nfs/var/cache/pacman
>
>
Ok, so it seems that these mounts are triggered not by the mount of /mnt/btrtop/root (see below). What is the output of
$ systemctl --reverse list-dependencies -- srv-nfs-var-cache-pacman.mount
[...]
>
> As mentioned, I have (temporarily) stopped unmounting these volumes
> and I just leave them mounted all the time. The logs now look like
> this:
>
> Aug 06 03:00:14 btrbk_run.sh[3022708]: mounting btrbk btrtop volumes...
> Aug 06 03:00:14 btrbk_run.sh[3022708]: INFO: [/mnt/btrtop/root] (1 of
> 3) was already mounted. Nothing to do.
> Aug 06 03:00:14 btrbk_run.sh[3022708]: INFO: [/mnt/btrtop/home] (2 of
> 3) was already mounted. Nothing to do.
> Aug 06 03:00:14 btrbk_run.sh[3022708]: INFO: [/mnt/btrtop/user] (3 of
> 3) was already mounted. Nothing to do.
This told another story. It seems that "btrbk" itself already try to mount the btrfs subvolume. I understood that it was the systemd unit to do that. Could you share the content of btrbk_run.sh ?
> Aug 06 03:00:14 btrbk_run.sh[3022708]: Finished mounting btrbk btrtop volumes.
> Aug 06 04:00:14 btrbk_run.sh[3033520]: mounting btrbk btrtop volumes...
> Aug 06 04:00:14 btrbk_run.sh[3033520]: INFO: [/mnt/btrtop/root] (1 of
> 3) was already mounted. Nothing to do.
> Aug 06 04:00:14 btrbk_run.sh[3033520]: INFO: [/mnt/btrtop/home] (2 of
> 3) was already mounted. Nothing to do.
> Aug 06 04:00:14 btrbk_run.sh[3033520]: INFO: [/mnt/btrtop/user] (3 of
> 3) was already mounted. Nothing to do.
> Aug 06 04:00:14 btrbk_run.sh[3033520]: Finished mounting btrbk btrtop volumes.
>
>>
>>>
>>> The path /var/cache/pacman is not a subvolume, but it resides on btrfs
>>> subvolume @btrtop/snapshot. @btrtop/snapshot is normally mounted at
>>> "/" but for btrfs tasks, it is also mounted at /mnt/btrtop/root. This
>>> additional mount operation seems to be causing these nested mounts of
>>> my bind mount for /srv/nfs/var/cache/pacman .
>>>
>>> P.S. I cannot test without using systemd. (I'm not even sure I
>>> remember how to use a non-systemd distro anymore!)
>>>
>>
>>
>> --
>> gpg @keyserver.linux.it: Goffredo Baroncelli <kreijackATinwind.it>
>> Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
--
gpg @keyserver.linux.it: Goffredo Baroncelli <kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
next prev parent reply other threads:[~2021-08-10 15:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 16:46 why is the same mount point repeatedly mounted in nested manner? Dave T
2021-08-05 17:47 ` Phillip Susi
2021-08-05 20:41 ` Dave T
2021-08-07 23:58 ` Adam Borowski
2021-08-09 4:50 ` Chris Murphy
2021-08-08 11:21 ` devel
2021-08-08 19:48 ` Dave T
2021-08-09 19:29 ` Goffredo Baroncelli
2021-08-09 20:15 ` Dave T
2021-08-10 15:43 ` Goffredo Baroncelli [this message]
2021-08-10 16:03 ` Dave T
2021-08-10 16:17 ` Goffredo Baroncelli
2021-08-10 16:27 ` Dave T
2021-08-10 20:17 ` Goffredo Baroncelli
2021-08-10 20:36 ` Dave T
2021-11-06 4:14 ` Dave T
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2074ef97-dbc2-d588-3000-622ffcf7e062@inwind.it \
--to=kreijack@inwind.it \
--cc=davestechshop@gmail.com \
--cc=devel@roosoft.ltd.uk \
--cc=kilobyte@angband.pl \
--cc=linux-btrfs@vger.kernel.org \
--cc=phill@thesusis.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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