Re: Corrupt btrfs filesystem recovery... What best instructions?

[Martin <m_btrfs@ml1.co.uk>]

What best to try next?

mount "-o recovery,noatime"

btrfsck:
    --repair                    try to repair the filesystem
    --init-csum-tree            create a new CRC tree
    --init-extent-tree          create a new extent tree

or is a "scrub" worthwhile?


The fail and switch to read-only occured whilst trying to delete a known
bad directory tree. No worries for losing the data in that.

But how best to clean up the filesystem errors?


Thanks,
Martin




On 03/10/13 17:56, Martin wrote:
> On 03/10/13 01:49, Martin wrote:
> 
>> Summary:
>>
>> Mounting "-o recovery,noatime" worked well and allowed a diff check to
>> complete for all but one directory tree. So very nearly all the data is
>> fine.
>>
>> Deleting the failed directory tree caused a call stack dump and eventually:
>>
>> kernel: parent transid verify failed on 915444822016 wanted 16974 found
>> 13021
>> kernel: BTRFS info (device sdc): failed to delete reference to
>> eggdrop-1.6.19.ebuild, inode 2096893 parent 5881667
>> kernel: BTRFS error (device sdc) in __btrfs_unlink_inode:3662: errno=-5
>> IO failure
>> kernel: BTRFS info (device sdc): forced readonly
>>
>>
>> Greater detail listed below.
>>
>> What next best to try?
>>
>> Safer to try again but this time with with "no_space_cache,no_inode_cache"?
>>
>> Thanks,
>> Martin
> 
> 
>> Next best step to try?
>>
>> Remount "-o recovery,noatime" again?
> 
> 
> In the meantime, trying:
> 
> btrfsck /dev/sdc
> 
> gave the following output + abort:
> 
> parent transid verify failed on 915444523008 wanted 16974 found 13021
> Ignoring transid failure
> btrfsck: cmds-check.c:1066: process_file_extent: Assertion `!(rec->ino
> != key->objectid || rec->refs > 1)' failed.
> id not match free space cache generation (1625)
> free space inode generation (0) did not match free space cache
> generation (1607)
> free space inode generation (0) did not match free space cache
> generation (1604)
> free space inode generation (0) did not match free space cache
> generation (1606)
> free space inode generation (0) did not match free space cache
> generation (1620)
> free space inode generation (0) did not match free space cache
> generation (1626)
> free space inode generation (0) did not match free space cache
> generation (1609)
> free space inode generation (0) did not match free space cache
> generation (1653)
> free space inode generation (0) did not match free space cache
> generation (1628)
> free space inode generation (0) did not match free space cache
> generation (1628)
> free space inode generation (0) did not match free space cache
> generation (1649)
> 
> 
> (There was no syslog output.)
> 
> Full btrfsck listing attached.
> 
> 
> Suggestions please?
> 
> Thanks,
> Martin