From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Eric Mesa <eric@ericmesa.com>
Cc: Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Issues with btrfs send/receive with parents
Date: Wed, 12 Jun 2019 08:43:00 +0300 [thread overview]
Message-ID: <21ecc5c2-7e4c-803e-5299-7ee150d6af4f@gmail.com> (raw)
In-Reply-To: <2008850.MjMmxLcJHu@supermario.mushroomkingdom>
[-- Attachment #1.1: Type: text/plain, Size: 2429 bytes --]
11.06.2019 7:19, Eric Mesa пишет:
> On Monday, June 10, 2019 11:39:53 PM EDT Andrei Borzenkov wrote:
>> 11.06.2019 4:10, Chris Murphy пишет:
>>> It's most useful if you show exact commands because actually it's not
>>> always obvious to everyone what the logic should be and the error
>>> handling doesn't always stop a user from doing something that doesn't
>>> make a lot of sense. We need to know the name of the rw subvolume; the
>>> command to snapshot it; the full send/receive command for that first
>>> snapshot; the command for a subsequent snapshot; and the command to
>>> incrementally send/receive it.
>>
>> And the actual output of each command, not description what user thinks
>> has happened.
>
> Here is a new session where I'll capture everything - well, on the defrag I'll
> do a snip.
>
> #btrfs fi defrag -v -r /home/
>
> ...there follows a list of files that just scrolls infinitely....
> /home/ermesa/.dropbox-dist/dropbox-lnx.x86_64-74.4.115/_bisect.cpython-37m-
> x86_64-linux-gnu.so
> /home/ermesa/.dropbox-dist/dropbox-lnx.x86_64-74.4.115/
> tornado.speedups.cpython-37m-x86_64-linux-gnu.so
> /home/ermesa/.bash_history
> total 1 failures
>
> # sync
>
> # btrfs sub snap -r /home/ /home/.snapshots/2019-06-10-2353
> Create a readonly snapshot of '/home/' in '/home/.snapshots/2019-06-10-2353'
>
> # btrfs send -vvv -p /home/.snapshots/2019-06-10-1718/ /home/.snapshots/
> 2019-06-10-2353/ | ssh root@tanukimario btrfs receive /media/backups/backups1/
> supermario-home
> At subvol /home/.snapshots/2019-06-10-2353/
> ERROR: link ermesa/.mozilla/firefox/n35gu0fb.default/bookmarkbackups/
> bookmarks-2019-06-10_679_I1bs5PtgsPwtyXvcvcRdSg==.jsonlz4 -> ermesa/.mozilla/
> firefox/n35gu0fb.default/bookmarkbackups/
> bookmarks-2019-06-09_679_I1bs5PtgsPwtyXvcvcRdSg==.jsonlz4 failed: No such file
> or directory
>
Does
ermesa/.mozilla/firefox/n35gu0fb.default/bookmarkbackups/bookmarks-2019-06-09_679_I1bs5PtgsPwtyXvcvcRdSg==.jsonlz4
actually exist in snapshot /home/.snapshots/2019-06-10-1718/ on source?
ls -lR
/home/.snapshots/2019-06-10-1718/ermesa/.mozilla/n35gu0fb.default/bookmarkbackups
What is the content of the same directory in matching snapshot on
destination?
Please show "btrfs subvolume list -qRu /home" for source and "btrfs
subvolume list -qRu /media/backups/backups1/supermario-home" for
destination.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2019-06-12 5:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 23:56 Issues with btrfs send/receive with parents Eric Mesa
2019-06-11 1:10 ` Chris Murphy
2019-06-11 3:39 ` Andrei Borzenkov
2019-06-11 4:19 ` Eric Mesa
2019-06-12 5:43 ` Andrei Borzenkov [this message]
2019-06-12 23:03 ` Eric Mesa
2019-06-12 23:11 ` Eric Mesa
2019-06-13 6:26 ` Andrei Borzenkov
2019-06-13 21:22 ` Eric Mesa
2019-06-14 3:55 ` Chris Murphy
2019-07-14 20:59 ` Eric Mesa
2019-06-18 4:15 ` Andrei Borzenkov
2019-06-11 3:47 ` Eric Mesa
2019-06-11 1:11 ` Remi Gauvin
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=21ecc5c2-7e4c-803e-5299-7ee150d6af4f@gmail.com \
--to=arvidjaar@gmail.com \
--cc=eric@ericmesa.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).