Re: Expected Received UUID

2018-08-01 Thread Gaurav Sanghavi
Hi, Here are the kernel details (uname -a): Device A (Debian 8.10): Linux DeviceA 3.16.0-4-amd64 #1 SMP Debian 3.16.51-3 (2017-12-13) x86_64 GNU/Linux Device B (Debian 8.11): Linux DeviceB 3.16.0-4-amd64 #1 SMP Debian 3.16.51-3 (2017-12-13) x86_64 GNU/Linux Device C (Debian 8.9): Linux DeviceC

Re: Expected Received UUID

2018-07-31 Thread Hans van Kranenburg
Hi, Can you please report the kernel versions you are using on every system (uname -a)? I would indeed expect the Received UUID value for C to have the same uuid as the original UUID of A, so the b00e8ba1 one. The send part, generating the send stream is done by the running kernel. The receive p

Re: Expected Received UUID

2018-07-31 Thread Cerem Cem ASLAN
Not an answer, but exactly same case: https://unix.stackexchange.com/questions/377914/how-to-test-if-two-btrfs-snapshots-are-identical 2018-07-31 20:42 GMT+03:00 Gaurav Sanghavi : > Hello everyone, > > While researching BTRFS for a project that involves backing up snapshots > from device A to dev

Expected Received UUID

2018-07-31 Thread Gaurav Sanghavi
Hello everyone, While researching BTRFS for a project that involves backing up snapshots from device A to device B before consolidating backups from device B to device C, I noticed that received UUID on snapshot on device C is not the same as received UUID for the same snapshot on device B. Here a