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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
