From: Dave T <davestechshop@gmail.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Cc: Phillip Susi <phill@thesusis.net>
Subject: Re: why is the same mount point repeatedly mounted in nested manner?
Date: Thu, 5 Aug 2021 16:41:03 -0400 [thread overview]
Message-ID: <CAGdWbB5+UOxxF21JxbzvVP3F-0zhDF4rpBc820fmc54Hyv-5WQ@mail.gmail.com> (raw)
In-Reply-To: <87eeb7pysj.fsf@vps.thesusis.net>
On Thu, Aug 5, 2021 at 1:49 PM Phillip Susi <phill@thesusis.net> wrote:
>
>
> Dave T <davestechshop@gmail.com> writes:
>
> > I'm using btrbk via a systemd timer. I have a daily and hourly timer
> > set up. Each timer starts by mounting the btrfs root, performing the
> > btrbk task, and unmounting the btrfs root.
>
> It looks like the unmounting is not being done, so it just keeps
> mounting it over again on the next backup.
>
Not exactly... that path should not be unmounted. I do not mount that
location explicitly for the btrbk tasks. It is mounted when the server
boots up with the bind mount line I showed in fstab:
/var/cache/pacman /srv/nfs/var/cache/pacman none bind 0 0
It should not be unmounted (or remounted) just because the top level
btrfs volume is (un)mounted for btrbk tasks. That's the part that is
confusing me.
There is no command associated with my btrbk tasks that mounts
/srv/nfs/var/cache/pacman (or /var/cache/pacman). There's no other
entry in fstab for it except the bind mount I showed.
next prev parent reply other threads:[~2021-08-05 20:41 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 [this message]
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
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=CAGdWbB5+UOxxF21JxbzvVP3F-0zhDF4rpBc820fmc54Hyv-5WQ@mail.gmail.com \
--to=davestechshop@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.