Patrik Lundquist posted on Fri, 01 Dec 2017 10:29:43 +0100 as excerpted:
> On 1 December 2017 at 08:18, Duncan <1i5t5.dun...@cox.net> wrote:
>>
>> When udev sees a device it triggers
>> a btrfs device scan, which lets btrfs know which devices belong to which
>> individual btrfs. But once it
Duncan,
Thank you for your thorough response to my problem. I am now wiser in
my understanding of how btrfs works in RAID1 thanks to your words.
Last night I worked with someone in the IRC channel and we essentially
came to the exact same conclusion. I used wipefs -a on the errant
drive. Rebooted
On 1 December 2017 at 08:18, Duncan <1i5t5.dun...@cox.net> wrote:
>
> When udev sees a device it triggers
> a btrfs device scan, which lets btrfs know which devices belong to which
> individual btrfs. But once it associates a device with a particular
> btrfs, there's nothing to unassociate it --
Eric Mesa posted on Thu, 30 Nov 2017 07:43:59 -0500 as excerpted:
> Hello,
>
> Not sure if this is a reportable bug, so I figured I'd start on the
> mailing list and then report a bug if it is a bug and not user error.
>
> Here is the original state of a RAID1 in which I wanted to replace the
>
Hello,
Not sure if this is a reportable bug, so I figured I'd start on the
mailing list and then report a bug if it is a bug and not user error.
Here is the original state of a RAID1 in which I wanted to replace the
smaller drive (except the /dev/sdX was different):
btrfs filesystem show
