From: A L <crimsoncottage@gmail.com>
To: linux-btrfs@vger.kernel.org
Cc: "Hermann Schwärzler" <hermann.schwaerzler@freirad.at>
Subject: Re: Btrfs incremental send | receive fails with Error: File not found
Date: Sat, 29 Jul 2017 01:26:43 +0200 [thread overview]
Message-ID: <c64a25d7-3845-e51a-c9b1-85de5190aceb@gmail.com> (raw)
In-Reply-To: <403536b6-2404-8589-3536-3a91ae769cd6@freirad.at>
On 7/28/2017 9:32 PM, Hermann Schwärzler wrote:
> Hi
>
> for me it looks like those snapshots are not read-only. But as far as
> I know for using send they have to be.
They are read-only.
# btrfs property get userData.20170727T1222/
ro=true
>
> At least
> https://btrfs.wiki.kernel.org/index.php/Incremental_Backup#Initial_Bootstrapping
>
> states "We will need to create a read-only snapshot ,,,"
>
> I am using send/receive (with read-only snapshots) on a regular basis
> and never had a problem like yours.
I have no good explanation. There are no problems reported on the
filesystems with Btrfs scrub or Btrfs check. Did you also replace files
with same name between snapshots?
>
> What are the commands you use to create your snapshots?
I used to do it in an hourly cron job like this.
# btrfs subvolume snapshot -r /mnt/storagePool/volume/userData/
/mnt/storagePool/snapshots/userData.`date +%Y.%m.%d-%H.%M.%S`
Now I use btrbk, but the command is the same and the problem is the same.
The problem I see seems similar to the issue fixed in
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f59627810e18d4435051d982b5d05cab18c6e653
but that commit should already be in kernel-4.13_rc2
>
> Greetings
> Hermann
>
> On 07/28/2017 07:26 PM, A L wrote:
>> I often hit the following error when doing incremental btrfs
>> send-receive:
>> Btrfs incremental send | receive fails with Error: File not found
>>
>> Sometimes I can do two-three incremental snapshots, but then the same
>> error (different file) happens again. It seems that the files were
>> changed or replaced between snapshots, which is causing the problems for
>> send-receive. I have tried to delete all snapshots and started over but
>> the problem comes back, so I think it must be a bug.
>>
>> The source volume is: /mnt/storagePool (with RAID1 profile)
>> with subvolume: volume/userData
>> Backup disk is: /media/usb-backup (external USB disk)
> [...]
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-07-28 23:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 17:26 Btrfs incremental send | receive fails with Error: File not found A L
2017-07-28 19:32 ` Hermann Schwärzler
2017-07-28 23:26 ` A L [this message]
2017-08-01 12:54 ` A L
2017-08-01 20:24 ` Cerem Cem ASLAN
2017-08-01 20:33 ` A L
2017-08-01 20:39 ` Cerem Cem ASLAN
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=c64a25d7-3845-e51a-c9b1-85de5190aceb@gmail.com \
--to=crimsoncottage@gmail.com \
--cc=hermann.schwaerzler@freirad.at \
--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 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).