Torsten Bronger

With btrfs-progs v5.4.1, I see ```shell root@myhost:/mnt/mymount# btrfs receive -E 0 . < send-output.btrfs At snapshot VirtualBox_brad_latest ERROR: cannot open /mnt/mymount//VirtualBox_brad_latest/o776-18725303-0: No such file or directory ERROR: chown o776-18725303-0 failed:...

If the errors occurs again, I will give it a try. I’ve never compiled a kernel, though.

Isn’t it even much worse? You don’t only need a Transifex account, you need a membership in the Mailpile team at Transifex. The translations are locked away currently.

I think the best solution is to copy the po files into the source tree, eventually using an automated process. The trouble that this may cause can be dealt with....

Thank you for working on this. What about file ordering? Does `ipfs --add -r` sort all path names in a future-proof way?

FWIW, if I issue a `btrfs send -p `, a sensibly small amount of data is produced, indicating an incremental backup. Can’t this be used to send the current snapshot...

I use send/receive for sync’ing a large VirtualBox .vdi file between my home server and my laptop. Both computers share a snapshot, which is snapshotted on the laptop, and then...

And yes, I mean the parent in “subvolume xyz”. By the way, I implemented a workaround by separating the sync’ing from the btrbk subvolume, and `cp --reflink` between both.

I think I have a use case for backupping a read-only subvolume. I use send/receive to sync two computers. I use the read-only property to mark the computer that is...

> I think correct behavior would be "backup readonly snapshots as usual, but only for once". They may have become read-write and then read-only again in the meantime.