• S
    Btrfs: fix wrong write offset when replacing a device · 115930cb
    Stefan Behrens 提交于
    Miao Xie reported the following issue:
    
    The filesystem was corrupted after we did a device replace.
    
    Steps to reproduce:
     # mkfs.btrfs -f -m single -d raid10 <device0>..<device3>
     # mount <device0> <mnt>
     # btrfs replace start -rfB 1 <device4> <mnt>
     # umount <mnt>
     # btrfsck <device4>
    
    The reason for the issue is that we changed the write offset by mistake,
    introduced by commit 625f1c8d.
    
    We read the data from the source device at first, and then write the
    data into the corresponding place of the new device. In order to
    implement the "-r" option, the source location is remapped using
    btrfs_map_block(). The read takes place on the mapped location, and
    the write needs to take place on the unmapped location. Currently
    the write is using the mapped location, and this commit changes it
    back by undoing the change to the write address that the aforementioned
    commit added by mistake.
    Reported-by: NMiao Xie <miaox@cn.fujitsu.com>
    Cc: <stable@vger.kernel.org> # 3.10+
    Signed-off-by: NStefan Behrens <sbehrens@giantdisaster.de>
    Signed-off-by: NJosef Bacik <jbacik@fusionio.com>
    115930cb
scrub.c 89.8 KB