btrfs receive --dump [options]
If --dump option is specified, btrfs receive will only do the validation of the stream, and print the stream metadata, one operation per line.
btrfs receive will fail in the following cases:
A subvolume is made read-only after the receiving process finishes successfully (see BUGS below).
Without this option the receiver side terminates only in case of an error on end of file.
Default value is 1. A value of 0 means no limit.
By default the mountpoint is searched in /proc/self/mounts. If /proc is not accessible, eg. in a chroot environment, use this option to tell us where this filesystem is mounted.
Does not require the path parameter. The filesystem remains unchanged.
If the intention is to create an exact copy, the receiving path should be protected from access by users until the receive operation has completed and the subvolume is set to read-only.
Additionally, receive does not currently do a very good job of validating that an incremental send stream actually makes sense, and it is thus possible for a specially crafted send stream to create a subvolume with reflinks to arbitrary files in the same filesystem. Because of this, users are advised to not use btrfs receive on send streams from untrusted sources, and to protect trusted streams when sending them across untrusted networks.