On Mon, 12 Aug 2013 14:33:02 +0300, Ilya Dryomov wrote:
Currently btrfs_device is allocated ad-hoc in a few different places,
and as a result not all fields are initialized properly. In particular,
readahead state is only initialized in device_list_add (at scan time),
and not in
On Fri, Aug 23, 2013 at 10:35 AM, Stefan Behrens
sbehr...@giantdisaster.de wrote:
This WARN_ON(1) is triggered with the device replace procedure because
BTRFS_DEV_REPLACE_DEVID is zero.
Ah, a dreaded 0 in C. What a screw up. This came from my rebuild
branch where btrfs_init_dev_replace_tgtdev
Currently btrfs_device is allocated ad-hoc in a few different places,
and as a result not all fields are initialized properly. In particular,
readahead state is only initialized in device_list_add (at scan time),
and not in btrfs_init_new_device (when the new device is added with
'btrfs dev
