[SOLVED] Cache Pool Size Delta

[RLA113]

My cache pool thinks it is running a 1.5TB drive, but hardware of the drive is 1TB. All is in RAID 1 on the pool.

 

I have setup a lower threshold to warn me. How do I fix the Cache drive to only see the pool as 1TB vs 1.5TB? Or some magical way do I have 1.5 on the pool? Any help/advice is appreciated.

 

[JorgeB]

Please post the diagnostics: Tools -> Diagnostics

[RLA113]

Here you go.

 

jarvis-diagnostics-20210202-1239.zip

 

Thank you for the quick reply! Let me know if there is something in the zip file I should be looking for.

Edited February 2, 2021 by RLA113

[JorgeB]

There's a device missing from the pool, hence the current reported capacity:

             Data      Metadata  System              
Id Path      RAID1     RAID1     RAID1    Unallocated
-- --------- --------- --------- -------- -----------
 1 /dev/sds1 465.00GiB   2.00GiB 32.00MiB   464.48GiB
 2 missing    61.00GiB   2.00GiB        -   -63.00GiB
 3 /dev/sdr1 404.00GiB         - 32.00MiB   527.48GiB
-- --------- --------- --------- -------- -----------
   Total     465.00GiB   2.00GiB 32.00MiB   928.96GiB

 

This also shows some data corruption, and likely why the missing device failed to be removed:

 

Feb  2 04:54:48 Jarvis kernel: BTRFS info (device sds1): bdev /dev/sds1 errs: wr 0, rd 0, flush 0, corrupt 7, gen 0
Feb  2 04:54:48 Jarvis kernel: BTRFS info (device sds1): bdev /dev/sdr1 errs: wr 0, rd 0, flush 0, corrupt 5, gen 0

 

Start by running memtest to check your RAM, then best to backup what you can from the pool and recreate, a scrub will indicate which files are corrupt.

[RLA113]

Awesome, thank you for the help! I will run memtest, if that does not work I will backup cache and recreate.

[ChatNoir]

If I understand what JorgeB says, the Memtest will not fix the issue, it is just to see if the cause would be a defective memory module.

 

You will have to recreate the pool as described above.

[JorgeB]

Yes, memtest is to try and confirm if it's a RAM problem, it won't fix the existing corrupt data, deleting the corrupt data should allow to remove the missing device from the pool, but possibly easier to juts backup, re-format and restore.

[RLA113]

Hey all, thank you very much for the help in diagnosing this issue. Turns out after running the memtest, it almost immediately found problems with the memory.

 

Have two sticks on the motherboard. Took one out, and the stick left ran just fine. Confirmed that it was the memory stick by swapping the good stick into the slot that was bad, and memtest ran just fine. Also put the bad stick in the good slot, and it found problems within 30 seconds.

 

Just bought the ram 4 months ago, upgrading from 16GB to 32GB, so trying to get an RMA going with G-skill, to get a replacement. Luckily with 32GB and two sticks, I can run off the 16GB for a while while trying to get a new ram stick. (I sold the 16GB pair.)

 

I run a weekly backup of the appdata on the cache drive and is the only thing I keep permanently on the cache, so not much lost after a format of the cache and a restore of the appdata.

 

After all of this, I am hoping my system is back to normal operating. Thank you again for all of the help troubleshooting.

[ChatNoir]

Too bad for your RAM, but at least it seems you found the root issue.

[RLA113]

Probably going to go with ECC memory this round

Edited February 5, 2021 by RLA113