* btrfs receive
@ 2023-06-27 17:57 Andreas Kielkopf
0 siblings, 0 replies; only message in thread
From: Andreas Kielkopf @ 2023-06-27 17:57 UTC (permalink / raw)
To: linux-btrfs
btrfs send is probably not used very often yet.
Lately I've been using btrfs send and btrfs receive a lot. In most
cases this works very well. But sometimes a somehow "exotic" snapshot
is created on the receive side. It seems complete and good, but it has
no receiveduuid.
This may happen 1 or 2 times out of 1000 send-receive operations.
It occurs reproducibly more frequently when btrfs is disrupted on the
receiving side. If e.g. while a receive is still running, another
snapshot in the same volume is deleted.
The receive continues. The delete is executed in between, but
extremely slowly. Even several deletes one after the other are
apparently executed correctly in parallel with the receive. Just
extremely slow.
With 10 such receives, in which deletes were inserted, 4 "exotic"
snapshots were created in which "only" the receiveduuid is missing.
Is this already known?
Greetings, and thanks for a really good file system
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2023-06-27 17:58 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-06-27 17:57 btrfs receive Andreas Kielkopf
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).