linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Chris Murphy <lists@colorremedies.com>,
	Anton Shepelev <anton.txt@gmail.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Spurious mount point
Date: Thu, 18 Oct 2018 15:51:32 +0300	[thread overview]
Message-ID: <2aebe72e-2864-9925-7346-ebdc83e0b6df@gmail.com> (raw)
In-Reply-To: <CAJCQCtR0zVDOS8u5zN2Ddo4+orrx62-L9e5GUnM=OWcwSitftQ@mail.gmail.com>

16.10.2018 0:33, Chris Murphy пишет:
> On Mon, Oct 15, 2018 at 3:26 PM, Anton Shepelev <anton.txt@gmail.com> wrote:
>> 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.
> 
> I wasn't aware that SUSE was now using the @ location for snapshots,

It does not "use @ for snapshots". It is using /@ as top level directory
for root layout. This was changed from using / directly quite some time
ago (2-3 years).

Snapshots are located in own subvolume which is either /.snapshots (if
your install is old) or /@/.snapshots and is always mounted as
/.snapshots in current root.

> or that it was using Btrfs for /home. For a while it's been XFS with a
> Btrfs sysroot.
> 

Default proposal is separate home partition with XFS, it can of course
be changed during installation.

Note that after default installation /@/.snapshots/1/snapshot is default
subvolume and *the* filesystem root, which gets mounted as "/". So it
could be result of bind-mount of /hana on /home/hana (/hana is resolved
to "default-subvolume"/hana => /@/.snapshots/1/snapshot/hana).

      parent reply	other threads:[~2018-10-18 12:51 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
2018-10-15 21:33     ` Chris Murphy
2018-10-15 22:01       ` Anton Shepelev
2018-10-18 12:51       ` Andrei Borzenkov [this message]

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=2aebe72e-2864-9925-7346-ebdc83e0b6df@gmail.com \
    --to=arvidjaar@gmail.com \
    --cc=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).