Revision adaa4b8e4d47eeb114513c2f7a172929154b94bd authored by Jan Schmidt on 21 March 2013, 14:30:23 UTC, committed by Josef Bacik on 28 March 2013, 13:51:26 UTC
When you take a snapshot, punch a hole where there has been data, then take
another snapshot and try to send an incremental stream, btrfs send would
give you EIO. That is because is_extent_unchanged had no support for holes
being punched. With this patch, instead of returning EIO we just return
0 (== the extent is not unchanged) and we're good.

Signed-off-by: Jan Schmidt <list.btrfs@jan-o-sch.net>
Cc: Alexander Block <ablock84@gmail.com>
Signed-off-by: Josef Bacik <jbacik@fusionio.com>
1 parent 4adaa61
History
File Mode Size
encrypted-keys
Kconfig -rw-r--r-- 2.4 KB
Makefile -rw-r--r-- 396 bytes
compat.c -rw-r--r-- 3.7 KB
gc.c -rw-r--r-- 10.7 KB
internal.h -rw-r--r-- 8.7 KB
key.c -rw-r--r-- 27.9 KB
keyctl.c -rw-r--r-- 40.2 KB
keyring.c -rw-r--r-- 32.3 KB
permission.c -rw-r--r-- 2.9 KB
proc.c -rw-r--r-- 8.6 KB
process_keys.c -rw-r--r-- 20.1 KB
request_key.c -rw-r--r-- 19.3 KB
request_key_auth.c -rw-r--r-- 6.6 KB
sysctl.c -rw-r--r-- 1.5 KB
trusted.c -rw-r--r-- 27.6 KB
trusted.h -rw-r--r-- 3.4 KB
user_defined.c -rw-r--r-- 4.9 KB

back to top