LimeB Posted January 24 Share Posted January 24 (edited) I had an unclean shutdown and coming back up, my cache drive is not mountable. Attached are my diags. Unmountable disk present: Cache • Samsung_SSD_970_EVO_Plus_2TB_S59CNM0RA30351D (nvme0n1) btrfs check with -n [1/7] checking root items [2/7] checking extents [3/7] checking free space tree free space info recorded 5227 extents, counted 5237 wanted offset 50535092224, found 50535088128 cache appears valid but isn't 50487885824 free space info recorded 1388 extents, counted 1398 There are still entries left in the space cache cache appears valid but isn't 59077820416 [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/mapper/nvme0n1p1 UUID: 511844b9-b3cc-4da0-bac2-e4c2d3fcff7f found 1031122690048 bytes used, error(s) found total csum bytes: 646066272 total tree bytes: 1119682560 total fs tree bytes: 158973952 total extent tree bytes: 107642880 btree space waste bytes: 243970093 file data blocks allocated: 5365445775360 referenced 955935105024 btrfs check with no modifier [1/7] checking root items [2/7] checking extents [3/7] checking free space tree free space info recorded 5227 extents, counted 5237 wanted offset 50535092224, found 50535088128 cache appears valid but isn't 50487885824 free space info recorded 1388 extents, counted 1398 There are still entries left in the space cache cache appears valid but isn't 59077820416 [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/mapper/nvme0n1p1 UUID: 511844b9-b3cc-4da0-bac2-e4c2d3fcff7f found 1031122690048 bytes used, error(s) found total csum bytes: 646066272 total tree bytes: 1119682560 total fs tree bytes: 158973952 total extent tree bytes: 107642880 btree space waste bytes: 243970093 file data blocks allocated: 5365445775360 referenced 955935105024 btrfs check with -L [1/7] checking root items [2/7] checking extents [3/7] checking free space tree free space info recorded 5227 extents, counted 5237 wanted offset 50535092224, found 50535088128 cache appears valid but isn't 50487885824 free space info recorded 1388 extents, counted 1398 There are still entries left in the space cache cache appears valid but isn't 59077820416 [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/mapper/nvme0n1p1 UUID: 511844b9-b3cc-4da0-bac2-e4c2d3fcff7f found 1031122690048 bytes used, error(s) found total csum bytes: 646066272 total tree bytes: 1119682560 total fs tree bytes: 158973952 total extent tree bytes: 107642880 btree space waste bytes: 243970093 file data blocks allocated: 5365445775360 referenced 955935105024 While it is not critical if I have to format the drive but hate to do it. Any thoughts on what I can try to fix it? diagnostics-20240124-0800.zip Edited January 24 by LimeB Quote Link to comment
Solution JorgeB Posted January 24 Solution Share Posted January 24 If the log tree is the only problem this may help: btrfs rescue zero-log /dev/mapper/nvme0n1p1 Then restart the array. Quote Link to comment
LimeB Posted January 24 Author Share Posted January 24 Awesome. I am back in business! Thank you. 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.