From: Remi Gauvin <remi@georgianit.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: No files in snapshot
Date: Wed, 4 Sep 2019 14:02:28 -0400 [thread overview]
Message-ID: <423454bc-aa78-daba-d217-343e266c15ee@georgianit.com> (raw)
In-Reply-To: <CAJCQCtRPUi3BLeSVqELopjC7ZvihOBi321_nxqcUG1jpgwq9Ag@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 756 bytes --]
On 2019-09-04 1:36 p.m., Chris Murphy wrote:
>>
>
> I don't really know how snapper works.
>
> The way 'btrfs subvolume snapshot' works, you must point it to a
> subvolume. It won't snapshot a regular directory and from what you
> posted above, there are no subvolumes in /var or /var/lib which means
> trying to snapshot /var/lib/ceph/osd/ceph-.... would fail. So maybe
> it's failing but snapper doesn't show the error. I'm not really sure.
>
In this case, his snapshots are all of the root.
I don't know how Ceph works, but since we already confirmed that there
are no subvolumes under /var, the only other explanation is that
/var/lib/ceph/osd/ceph-<n> is a submount
What is the the result of running:
mount | grep /var
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2019-09-04 18:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 9:33 No files in snapshot Thomas Schneider
2019-08-27 22:24 ` Chris Murphy
2019-08-28 14:45 ` Thomas Schneider
2019-09-04 17:36 ` Chris Murphy
2019-09-04 18:02 ` Remi Gauvin [this message]
2019-09-04 19:07 ` Chris Murphy
2019-09-04 20:52 ` Oliver Freyermuth
2019-09-05 8:50 ` Thomas Schneider
2019-09-05 18:31 ` Oliver Freyermuth
2019-09-04 9:24 ` Thomas Schneider
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=423454bc-aa78-daba-d217-343e266c15ee@georgianit.com \
--to=remi@georgianit.com \
--cc=linux-btrfs@vger.kernel.org \
/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.