From: Anton Shepelev <anton.txt@gmail.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Spurious mount point
Date: Tue, 16 Oct 2018 00:26:01 +0300 [thread overview]
Message-ID: <20181016002601.5517a4ea66c2c9c5dbdb5471@gmail.com> (raw)
In-Reply-To: <CAJCQCtSz+=uwXUFGxagoUOYxy99eCJGG-ezLVh0RO=vL=LReEg@mail.gmail.com>
Chris Murphy to Anton Shepelev:
> > How can I track down the origin of this mount point:
> >
> > /dev/sda2 on /home/hana type btrfs (rw,relatime,space_cache,subvolid=259,subvol=/@/.snapshots/1/snapshot/hana)
> >
> > if it is not present in /etc/fstab? I shouldn't like to
> > find/grep thoughout the whole filesystem.
>
> Sounds like some service taking snapshots regularly is
> managing this. Maybe this is Mint or Ubuntu and you're
> using Timeshift?
It is SUSE Linux and (probably) its tool called `snapper',
but I have not found a clue in its documentation.
> Maybe it'll show up in the journal if you add boot
> parameter 'systemd.log_level=debug' and reboot; then use
> 'journalctl -b | grep mount' and it should show all
> instances logged instances of mount events: systemd,
> udisks2, maybe others?
I will try that as soon as the client lets me reboot that
machine.
--
() ascii ribbon campaign -- against html e-mail
/\ http://preview.tinyurl.com/qcy6mjc [archived]
next prev parent reply other threads:[~2018-10-15 21:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 15:05 Spurious mount point Anton Shepelev
2018-10-15 20:22 ` Chris Murphy
[not found] ` <CAJCQCtSz+=uwXUFGxagoUOYxy99eCJGG-ezLVh0RO=vL=LReEg@mail.gmail.com>
2018-10-15 21:26 ` Anton Shepelev [this message]
2018-10-15 21:33 ` Chris Murphy
2018-10-15 22:01 ` Anton Shepelev
2018-10-18 12:51 ` Andrei Borzenkov
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=20181016002601.5517a4ea66c2c9c5dbdb5471@gmail.com \
--to=anton.txt@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/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;
as well as URLs for NNTP newsgroup(s).