Can't create new RAID1 pool, changing RAID in single pool doesn't work

Bugs
1

I just upgraded to 3.8-4. I made a new RAID1 pool with three disks and discovered that the pool got created as Single. I tried several times to make a RAID1 pool using two and three disks and it was always created as Single. The reported free space was consistent with an actual Single pool so it’s not an instrumentation error.

I next tried to create a Single pool with sda and changed its level to RAID1 by adding sdb to it, and it seemed to succeed until I refreshed the pool details page. sda was no longer a member of the pool and sdb was the only member of the pool, which was now Single.

I finally tried to make a RAID5 out of the three disks and it seemed to be successful.

Right now I can’t make a RAID1 pool in any way I can find.

2

I think i read something about this in another thread.

The solution as I remember it, was to create the RAID1 pool, ignore that it was marked as a single drive, and then run a balance.

When this is finished, the pool should show up as RAID1.

This is something you could try :slight_smile:

3

@tcmbackwards I am hoping that this will go away with next kernel update. Here’s the issue for it anyway in case we need to add any code on top of btrfs. For now, do try rebalance and it should hopefully sort things out.

4

When I rebooted it, the pool showed up as RAID 1 with two disks and I was able to add the third disk to it. Weird.