Revision 2cac13e41bf5b99ffc426bd28dfd2248df1dfa67 authored by Liu Bo on 09 February 2012, 10:17:41 UTC, committed by David Sterba on 15 February 2012, 15:40:23 UTC
A user reported a bug of btrfs's trim, that is we will trim 0 bytes after a device delete. The reproducer: $ mkfs.btrfs disk1 $ mkfs.btrfs disk2 $ mount disk1 /mnt $ fstrim -v /mnt $ btrfs device add disk2 /mnt $ btrfs device del disk1 /mnt $ fstrim -v /mnt This is because after we delete the device, the block group may start from a non-zero place, which will confuse trim to discard nothing. Reported-by: Lutz Euler <lutz.euler@freenet.de> Signed-off-by: Liu Bo <liubo2009@cn.fujitsu.com>
1 parent 6af021d
| File | Mode | Size |
|---|---|---|
| .gitignore | -rw-r--r-- | 151 bytes |
| Kconfig | -rw-r--r-- | 5.3 KB |
| Makefile | -rw-r--r-- | 2.3 KB |
| gen_init_cpio.c | -rw-r--r-- | 13.1 KB |
| initramfs_data.S | -rw-r--r-- | 1.3 KB |
Computing file changes ...
