BTRFS corruption after hardware issues

BTRFS corruption after hardware issues

[Brian B]

[-- Attachment #1.1: Type: text/plain, Size: 890 bytes --]

I had a stick of memory go bad in my server, and after removing it my
BTRFS filesystem seems to be damaged.

If I mount the volume rw and try to use the volume, most actions will
hang, and I get btrfs-transactio related errors in the logs.

'btrfsck --repair' seems to sit in a loop, printing the same messages
about attempting to repair a dozen or so inodes over and over again.

I can mount the volume with '-o ro,recovery', but some folders are
missing from the current live volume.  It looks like some of the nodes
are still there, just orphaned or something.  For instance, from btrfsck:


root 551 inode 102353 errors 2001, no inode item, link count wrong
        unresolved ref dir 261 index 0 namelen 5 name dir1 filetype 2
errors 6, no dir index, no inode ref


So is there some way I can mount that as a root, or re-link it to the
rest of the tree somehow?


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

Re: BTRFS corruption after hardware issues

[Brian B]

[-- Attachment #1.1: Type: text/plain, Size: 1241 bytes --]

On 04/03/2017 11:26 AM, Brian B wrote:
> I had a stick of memory go bad in my server, and after removing it my
> BTRFS filesystem seems to be damaged.
>
> If I mount the volume rw and try to use the volume, most actions will
> hang, and I get btrfs-transactio related errors in the logs.
>
> 'btrfsck --repair' seems to sit in a loop, printing the same messages
> about attempting to repair a dozen or so inodes over and over again.
>
> I can mount the volume with '-o ro,recovery', but some folders are
> missing from the current live volume.  It looks like some of the nodes
> are still there, just orphaned or something.  For instance, from btrfsck:
>
>
> root 551 inode 102353 errors 2001, no inode item, link count wrong
>         unresolved ref dir 261 index 0 namelen 5 name dir1 filetype 2
> errors 6, no dir index, no inode ref
>
>
> So is there some way I can mount that as a root, or re-link it to the
> rest of the tree somehow?
>
So, turns out that although the directories don't SHOW in an ls, I can
still navigate to them:


# ls __current/pictures

mom

# ls __current/pictures/dad

2006-2008


I'll be trying to get the data off these later tonight when I can plug
in an extra HDD.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]