Hi there,

this morning my server shows that the filessystem from the cache pools is unmountable.
In the array maintanance mode I done the brtrfs check from the gui with this result:
 

Quote

 

[1/7] checking root items

[2/7] checking extents data extent[1557454716928, 4096] referencer count mismatch (root 5 owner 36971 offset 2959822848) wanted 0 have 1 data extent[1557454716928, 4096] bytenr mimsmatch, extent item bytenr 1557454716928 file item bytenr 0 data extent[1557454716928, 4096] referencer count mismatch (root 65541 owner 36971 offset 2959822848) wanted 1 have 0 backpointer mismatch on [1557454716928 4096] ERROR: errors found in extent allocation tree or chunk allocation

[3/7] checking free space tree

[4/7] checking fs roots

[5/7] checking only csums items (without verifying data)

[6/7] checking root refs

[7/7] checking quota groups skipped (not enabled on this FS) Opening filesystem to check... Checking filesystem on /dev/sdc1 UUID: 832f2c25-defe-4d68-80e1-2d9e8545fa35 found 348794531840 bytes used, error(s) found total csum bytes: 315368728 total tree bytes: 681279488 total fs tree bytes: 244301824 total extent tree bytes: 53100544 btree space waste bytes: 122260750 file data blocks allocated: 906466258944 referenced 343156350976

 

Now I cant mount the cache pool with all my data and docker configs on it. Any idea to get this back working?

 

Thanks. BR ET

Edited June 24, 20242 yr by EinfachToll

Please post the diagnostics.
 

server-diagnostics-20240624-1336.zip

If the log tree is the only issue this may help:

 

btrfs rescue zero-log /dev/sdc1

 

Then re-start the array

I was able to backup all data from the pool with this comand --> btrfs restore -v /dev/sdc1 /mnt/user/Backup/POOLBACKUP

 

shall i now try your command?

 

Yep.

Sorry, with array off, on or in maintanace mode? @JorgeB

Edited June 24, 20242 yr by EinfachToll

In this case it doesn't matter, it can even be done with the array in normal mode, since the fs is not mounted.

Array is back online. Thanks hope this is fixed now. Thank you!

Hi, i still have massive issues, now the docker container wont start anymore and in the system protocoll i see a lot of BTRFS issues...

 

 

server-diagnostics-20240624-1703.zip

loop2 is where the docker.img file gets mounted so that suggests its contents are corrupt.  It could also be by-product of the pool containing it being corrupt.

 

You should consider deleting it; recreating a new empty file and then reloading its contents via Apps->Previous Apps.

Whatever I do it shows allways readonly filesystem... What can I do now?

 

That suggests the pool filesystem has other issues, suggest that you backup and then re-format.