diff options
| author | Miao Xie <miaox@cn.fujitsu.com> | 2014-07-24 11:37:06 +0800 |
|---|---|---|
| committer | Chris Mason <clm@fb.com> | 2014-08-19 08:52:16 -0700 |
| commit | ff61d17c6324d1b483fbbc5144f09668c24ff60c (patch) | |
| tree | 53f4d493f94b4909376d3278c656f4678d9451bd /crypto | |
| parent | 2c91943b5066314a8bb9f0a65584e5e4cd92ea63 (diff) | |
| download | op-kernel-dev-ff61d17c6324d1b483fbbc5144f09668c24ff60c.zip op-kernel-dev-ff61d17c6324d1b483fbbc5144f09668c24ff60c.tar.gz | |
Btrfs: Fix the problem that the replace destroys the seed filesystem
The seed filesystem was destroyed by the device replace, the reproduce
method is:
# mkfs.btrfs -f <dev0>
# btrfstune -S 1 <dev0>
# mount <dev0> <mnt>
# btrfs device add <dev1> <mnt>
# umount <mnt>
# mount <dev1> <mnt>
# btrfs replace start -f <dev0> <dev2> <mnt>
# umount <mnt>
# mount <dev0> <mnt>
It is because we erase the super block on the seed device. It is wrong,
we should not change anything on the seed device.
Signed-off-by: Miao Xie <miaox@cn.fujitsu.com>
Reviewed-by: David Sterba <dsterba@suse.cz>
Signed-off-by: Chris Mason <clm@fb.com>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions
