From: Andrei Borzenkov <arvidjaar@gmail.com>
To: MASAKI Haruka <reasonset@inflaton.co.jp>, linux-btrfs@vger.kernel.org
Subject: Re: Some file lost when send back snapshot.
Date: Thu, 25 Apr 2019 20:55:59 +0300 [thread overview]
Message-ID: <aa5623ca-e1c2-4499-75ee-be818acf3333@gmail.com> (raw)
In-Reply-To: <20190425223457.5a7dfd20@hydrangea>
25.04.2019 16:34, MASAKI Haruka пишет:
> I send snapshot from backup volume, and send new snaopshot to backup volume,
> and some file lost in received volume.
>
> In detail:
>
> 1. Host A has new Btrfs volume and Host B have two backuped readonly subvolumes (190312-010100, 190315-001000).
> 2. Host B send 190315-001000 subvolume to Host A.
> 3. Host A completely received (all files exist.)
> 4. Host B took new readonly snapshot "back1" on 190315-001000 (all files exist.)
> 5. Host B send back1 with `-p 190315-001000` to Host A (some file lost.)
> 6. Host B took new read-writable snapshot "world" on back1 (all files exist.)
> 7. Host B modified world.
> 8. Host B took new readonly snapshot "back2" on world (all files exist.)
> 9. Host B send back2 with `-p 190315-001000` to Host A (some file lost.)
> 10. Deleted received snapshot and Host B send back2 with `-p back1` to Host A (some file lost.)
>
Please show
1. Full protocol of commands you executed (commands and their output),
e.g. captured using script.
2. Commands used to determine missing files on both source and receive
sides.
3. Listing of subvolumes on both source and receive sides with
btrfs sub li -Rqu /mount/point
> Kernel
> 5.0.5-1-MANJARO
>
> Btrfs progs
> btrfs-progs 4.20.2-1
>
>
> What I should do?
>
> Thanks.
>
>
>
> Masaki Haruka
>
next prev parent reply other threads:[~2019-04-25 17:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 13:34 Some file lost when send back snapshot MASAKI Haruka
2019-04-25 17:55 ` Andrei Borzenkov [this message]
2019-04-26 4:50 ` MASAKI Haruka
2019-04-26 17:30 ` Andrei Borzenkov
2019-04-26 18:12 ` MASAKI Haruka
2019-04-26 18:27 ` Andrei Borzenkov
2019-04-27 5:50 ` MASAKI Haruka
2019-04-27 20:54 ` Chris Murphy
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=aa5623ca-e1c2-4499-75ee-be818acf3333@gmail.com \
--to=arvidjaar@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=reasonset@inflaton.co.jp \
/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