When trying to add a new caching drive I did not look it up at first. There was my first mistake.

 

I just added a second pool, lauched the array, stopped it again and added my drive into the empty pool. 

Then I noticed I had one 900 or so GB of space on my cache. I stopped the array and removed the drive from the cache and started it again thinking it would somehow revert to normal. (it did not) 

 

Now my cache is in following state: 

 

and I do not know how to fix it. I do still have the drive I added and removed (non formatted nor touched)

 

and I rebooted to safe mode.

 

 

 

 

So to be clear I would like to go back and have my cache being only the sdf drive and I will follow a tutorial to replace it with de sdb drive since I found plenty of documentation.

arialis-mserver-diagnostics-20221219-2130.zip

Edited December 19, 20223 yr by Alpha.Ars

40 minutes ago, Alpha.Ars said:

added a second pool, lauched the array, stopped it again and added my drive into the empty pool.

Are you sure you didn't add the drive into the cache pool?

40 minutes ago, trurl said:

Are you sure you didn't add the drive into the cache pool?

 

 

Yes I did. I got confused with a text I read before posting my question.

 

 

Edited December 19, 20223 yr by Alpha.Ars

Please post output of:

btrfs fi show

 

On 12/20/2022 at 10:53 AM, JorgeB said:

Please post output of:

btrfs fi show

 

Label: none  uuid: a6dcc4fb-21bc-4244-9872-dc35d278e2f1
        Total devices 2 FS bytes used 166.30GiB
        devid    1 size 232.88GiB used 176.02GiB path /dev/sdf1
        *** Some devices missing

 

array is stropped and this is the situation right now:

Edited December 21, 20223 yr by Alpha.Ars

Post the output of

btrfs-select-super -s 1 /dev/sdb1

 

And after doing the again output of

btrfs fi show