Re: RAID1 disk upgrade method

["Austin S. Hemmelgarn" <ahferroin7@gmail.com>]

On 2016-01-27 18:55, Sean Greenslade wrote:
> On Wed, Jan 27, 2016 at 05:45:49PM -0500, Sean Greenslade wrote:
>> OK, disks have arrived, and I've completed the first replace.
>> Interestingly enough, the replace seems to have succeeded, however btrfs
>> fi show doesn't seem to think so.
>>
>> Dmesg:
>> [Wed Jan 27 13:03:09 2016] BTRFS info (device sdb1): disk space caching
>> is enabled
>> [Wed Jan 27 13:03:09 2016] BTRFS: has skinny extents
>> [Wed Jan 27 13:03:09 2016] BTRFS: bdev /dev/sdb1 errs: wr 0, rd 186,
>> flush 0, corrupt 0, gen 0
>> [Wed Jan 27 13:05:23 2016]  sdc: sdc1
>> [Wed Jan 27 13:05:25 2016]  sdc: sdc1
>> [Wed Jan 27 13:08:37 2016] BTRFS: dev_replace from /dev/sdb1 (devid 2)
>> to /dev/sdc1 started
>> [Wed Jan 27 16:34:49 2016] BTRFS: dev_replace from /dev/sdb1 (devid 2)
>> to /dev/sdc1 finished
>>
>> Btrfs fi show:
>> warning, device 3 is missing
>> warning, device 3 is missing
>> warning devid 3 not found already
>> Label: none  uuid: 490b8b7c-59c4-45dc-ac63-6a90f0966776
>>          Total devices 2 FS bytes used 1.45TiB
>> 		devid    1 size 1.82TiB used 1.52TiB path /dev/sda1
>> 		*** Some devices missing
>>
>> I haven't rebooted or remounted yet, so I'm curious if this is a bug,
>> a normal thing that is fixed by a reboot, or what.
>
> Got the opportunity to reboot, and things appear to be OK. Still, I
> would expect replace to work without requiring a reboot, so this may
> still be a bug. I'm running a scrub to verify things, and once that
> completes I'll do the second replace and see if I encounter the same
> problem.
That is unusual, it's supposed to work without needing a reboot or 
rescan, so I think you may have found a bug.