Revision ee20a98314e52a6675e94d1a07ca205ffdf09a72 authored by Josef Bacik on 11 July 2013, 14:34:59 UTC, committed by Chris Mason on 09 August 2013, 23:30:09 UTC
I noticed while running multi-threaded fsync tests that sometimes fsck would complain about an improper gap. This happens because we fail to add a hole extent to the file, which was happening when we'd split a hole EM because btrfs_drop_extent_cache was just discarding the whole em instead of splitting it. So this patch fixes this by allowing us to split a hole em properly, which means that added holes actually get logged properly and we no longer see this fsck error. Thankfully we're tolerant of these sort of problems so a user would not see any adverse effects of this bug, other than fsck complaining. Thanks, Signed-off-by: Josef Bacik <jbacik@fusionio.com> Signed-off-by: Chris Mason <chris.mason@fusionio.com>
1 parent ed8c491
| File | Mode | Size |
|---|---|---|
| .gitignore | -rw-r--r-- | 151 bytes |
| Kconfig | -rw-r--r-- | 5.6 KB |
| Makefile | -rw-r--r-- | 2.3 KB |
| gen_init_cpio.c | -rw-r--r-- | 13.0 KB |
| initramfs_data.S | -rw-r--r-- | 1.3 KB |
Computing file changes ...
