You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Send/receive has received support for a new send protocol in kernel 5.19. Btrfs-sxbackup should default to the newest protocol supported given that the kernel version and btrfs-progs version supports it.
Using "btrfs send --proto 0" should be a safe way to do it.
The text was updated successfully, but these errors were encountered:
madsl
changed the title
Add "--proto 0" to send/receive if kernel version is >= 5.19
Add "--proto 0" to send/receive
Oct 27, 2022
doesn't this break backups running older kernels. imho btrfs send / receive should negotiate their protocol version and until that happens its probably better sticking with default. what's the concrete benefits of running newest protocol via --proto 0?
--proto <N>
use send protocol version N
The default is 1, which was the original protocol version. Version 2 encodes file data slightly more efficiently; it is also required for sending compressed data directly
(see --compressed-data). Version 2 requires at least btrfs-progs 5.18 on both the sender and receiver and at least Linux 5.18 on the sender. **Passing 0 means to use the
highest version supported by the running kernel.**
So if I understand this correctly, I think proto 0 means it finds out itself what is safe.
Send/receive has received support for a new send protocol in kernel 5.19. Btrfs-sxbackup should default to the newest protocol supported given that the kernel version and btrfs-progs version supports it.
Using "btrfs send --proto 0" should be a safe way to do it.
The text was updated successfully, but these errors were encountered: