diff options
| author | Liu Bo <liubo2009@cn.fujitsu.com> | 2012-02-09 18:17:41 +0800 |
|---|---|---|
| committer | David Sterba <dsterba@suse.cz> | 2012-02-15 16:40:23 +0100 |
| commit | 2cac13e41bf5b99ffc426bd28dfd2248df1dfa67 (patch) | |
| tree | b74e7e863b7d7c2e116dc6754d8faf701c0aa3c9 /fs/udf/partition.c | |
| parent | 6af021d8fc3bcce790e7fbb391e39c5920fa3f71 (diff) | |
| download | linux-2cac13e41bf5b99ffc426bd28dfd2248df1dfa67.tar.bz2 | |
Btrfs: fix trim 0 bytes after a device delete
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>
Diffstat (limited to 'fs/udf/partition.c')
0 files changed, 0 insertions, 0 deletions