public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Schneider <74cmonty@gmail.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: No files in snapshot
Date: Wed, 4 Sep 2019 11:24:22 +0200	[thread overview]
Message-ID: <2ba86d8c-8849-eb61-5d9d-dfe024e13127@gmail.com> (raw)
In-Reply-To: <CAJCQCtTs4jBw_mz3PqfMAhuHci+UxjtMNYD7U4LJtCoZxgUdCg@mail.gmail.com>

Can you share any update on this issue?

-------------------------------

Hi,

I was thinking of this, too. But it does not apply.
root@ld5507:~# btrfs su list -to /var/lib
ID      gen     top level       path
--      ---     ---------       ----
root@ld5507:~# btrfs su list -to /var
ID      gen     top level       path
--      ---     ---------       ----

And there are files in other directories:
root@ld5507:~# ls -l /.snapshots/158/snapshot/var/lib/ceph/mgr/ceph-ld5507/
insgesamt 4
-rw-r--r-- 1 ceph ceph 61 Mai 28 14:33 keyring

root@ld5507:~# ls -l /.snapshots/158/snapshot/var/lib/ceph/mon/ceph-ld5507/
insgesamt 12
-rw------- 1 ceph ceph  77 Mai 28 14:33 keyring
-rw-r--r-- 1 ceph ceph   8 Mai 28 14:33 kv_backend
-rw-r--r-- 1 ceph ceph   3 Aug 23 09:41 min_mon_release
drwxr-xr-x 1 ceph ceph 244 Aug 26 18:37 store.db

Only this directories 
/.snapshots/158/snapshot/var/lib/ceph/osd/ceph-<id>/ are empty:
root@ld5507:~# ls -l /.snapshots/158/snapshot/var/lib/ceph/osd/ceph-219/
insgesamt 0

To create a snapshot I run this command:
snapper create --type single --description "validate 
/var/lib/ceph/osd/ceph-<n>"



Am 28.08.2019 um 00:24 schrieb Chris Murphy:
> On Tue, Aug 27, 2019 at 3:33 AM Thomas Schneider <74cmonty@gmail.com> 
> wrote:
>> However, I run into an issue and need to restore various files.
>>
>> I thought that I could simply take the files from a snapshot created 
>> before.
>> However, the files required don't exist in any snapshot!
>>
>> Therefore I have created a new snapshot manually to verify if the files
>> will be included, but there's nothing.
> Snapshots are not recursive on Btrfs. The snapshot will not extend
> into nested subvolumes. Check to see if you are snapshotting the
> proper subvolume.
>
> # btrfs sub list -to /var/lib
> # btrfs sub list -to /var/
>
> In some sense these are redundant, I'm not sure if your /var/lib is a
> subvolume or not. Also please include the exact snapshot command
> you're making.
>



      parent reply	other threads:[~2019-09-04  9:24 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
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 [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=2ba86d8c-8849-eb61-5d9d-dfe024e13127@gmail.com \
    --to=74cmonty@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