What are the typical usecase of "btrfs check --init-extent-tree"?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



My RAID-1 FS have multiple "backpointer mismatch" errors. "btrfs check
--repair" doesn't help but only increases the number of errors.
Initially, only 2 roots were affected (uncleanly deleted snapshots I
suppose). But after I ran "check --repair" new "check --readonly"
returns such errors on almost every root!
You can read a small prehistory in this mailing list thread:
https://www.mail-archive.com/linux-btrfs@xxxxxxxxxxxxxxx/msg64640.html
Recently I decided to resume my attempts to recover the FS and, at
some point I booted into my system (Fedora 25 with 4.11.3-200 kernel
with patch from the thread mentioned above). A Snapper daemon tried to
remove some corrupted snapshot and, as result, triggered btrfs-cleaner
bug. Now I can neither RW-mount the FS nor run scrub (scrub is
"aborted" in 00:00:00 after start).

How does "--init-extent-tree" deal with backref problems? Will those
backrefs completely reconstructed?

Can similar "backref not found" and "backpointer mismatched" errors
have very different causes and different fix scenarios?

-- 
Ivan Sizov
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux