fix empty subvolume send and receive
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
btrfs-progs (Ubuntu) |
Fix Released
|
Undecided
|
Stéphane Graber | ||
Zesty |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
The original report can be found here:
https:/
== Rationale ==
The previous btrfs bugfix while it fixed the issue we found back then, also introduced a regression for some other users. This issue was reported upstream and fixed by Christian (author of the original patch). This regression fix has been merged by btrfs upstream and should be included in Ubuntu.
== Testcase ==
The reproducer for this issue is:
truncate -s 10GB pool.btrfs
mkfs.btrfs pool.btrfs
mount -t btrfs pool.btrfs /mnt
btrfs subvolume create /mnt/a
btrfs subvolume snapshot /mnt/a /mnt/snap-a
btrfs send /mnt/snap-a | btrfs receive /mnt/a
should incorrectly fail with
ERROR: empty stream is not considered valid
whereas it should actually succeed.
== Regression potential ==
The previous fix for this issue introduced a regression, so it's clearly not impossible that this may introduce yet another one.
Both this and the previous patch were reviewed and merged upstream, including a testcase, so nothing that we know about or that upstream knows about should regress.
btrfs upstream (https:/
affects: | btrfs (Ubuntu) → btrfs-progs (Ubuntu) |
tags: |
added: verification-done removed: verification-needed |
Uploaded to artful and zesty.