blocks|key|1801239|text|浏览网页时，我发现很多答案建议使用btrfs-zero-log清除btrfs的内部日志。我认为btrfsck可以帮上忙，但最终我发现了正式建议，即首先启动一个+https://btrfs.wiki.kernel.org/index.php/Manpage/btrfs-scrub，然后再采取其他行动！|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|BOLD|entityRanges|data|1801240|因此，如果您仍然可以挂载您的文件系统，只需运行btrfs+scrub+/path/to/mountpoint即可。也许在我的案子里起作用了。|1801241|entityMap|0|LINK|mutability|MUTABLE|url|https://unix.stackexchange.com/questions/32440/how-do-i-fix-btrfs|1|https://btrfs.wiki.kernel.org/index.php/Btrfsck|2|3|https://btrfs.wiki.kernel.org/index.php/Manpage/btrfs-scrub^0|H|E|X|5|1B|7|21|6|B|2|0|1B|7|1|1V|4|2|28|1N|3|0|N|V|0^^$0|@$1|2|3|4|5|6|7|V|8|@$9|W|A|X|B|C]|$9|Y|A|Z|B|C]|$9|10|A|11|B|C]|$9|12|A|13|B|D]]|E|@$9|14|A|15|1|16]|$9|17|A|18|1|19]|$9|1A|A|1B|1|1C]|$9|1D|A|1E|1|1F]]|F|$]]|$1|G|3|H|5|6|7|1G|8|@$9|1H|A|1I|B|C]]|E|@]|F|$]]|$1|I|3|-4|5|6|7|1J|8|@]|E|@]|F|$]]]|J|$K|$5|L|M|N|F|$O|P]]|Q|$5|L|M|N|F|$O|R]]|S|$5|L|M|N|F|$O|R]]|T|$5|L|M|N|F|$O|U]]]]

Surfing the web I found a lot of <a href="https://unix.stackexchange.com/questions/32440/how-do-i-fix-btrfs">answers</a> recommending to clear <code>btrfs</code>' internal log by using <code>btrfs-zero-log</code>. I thought <a href="https://btrfs.wiki.kernel.org/index.php/Btrfsck" rel="nofollow noreferrer"><code>btrfsck</code></a> could help but eventually I discovered the <a href="https://btrfs.wiki.kernel.org/index.php/Btrfsck" rel="nofollow noreferrer">official recommendation</a> which is to first just start a <a href="https://btrfs.wiki.kernel.org/index.php/Manpage/btrfs-scrub" rel="nofollow noreferrer"><code>btrfs scrub</code></a> before taking other actions!

So just run <code>btrfs scrub /path/to/mountpoint</code> if you too can still mount your filesystem. And maybe it works like in my case.

blocks|key|88582|text|我也遇到了类似的情况：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|88583|日志中满是parent+transid+verify+failed+on+109973766144+wanted+1823+found+1821|ordered-list-item|offset|length|style|CODE|88584|dmesg充满了BTRFS+info+(device+sda):+no+csum+found+for+inode+16485445+start+73728和BTRFS+warning+(device+sda):+csum+failed+ino+16485465+off+36864+csum+2268363541+expected+csum+0。|88585|my+system的配置|88586|有3个nfs股份的NAS|88587|BTRFS文件系统|88588|Rockstor操作系统|88589|RAID+10设置|88590|附加信息|BOLD|88591|btrfs挂载变为只读。|88592|btrfs-+ERROR:+scrubbing+/dev/md124p2+failed+for+device+id+1:+ret=-1,+errno=5失败|88593|我通过删除nfs导出来解决这个问题。从/etc/export/然后重新装订卷，瞧，一切都很好|88594|更新2018年1月29日：工作了几天就回到了原来的状态|88595|entityMap^0|0|5|1V|0|8|1X|26|2M|0|0|0|0|0|0|0|4|0|0|7|1X|0|0|0|D|0^^$0|@$1|2|3|4|5|6|7|17|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|18|8|@$E|19|F|1A|G|H]]|9|@]|A|$]]|$1|I|3|J|5|D|7|1B|8|@$E|1C|F|1D|G|H]|$E|1E|F|1F|G|H]]|9|@]|A|$]]|$1|K|3|L|5|6|7|1G|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|1H|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|1I|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|1J|8|@]|9|@]|A|$]]|$1|S|3|T|5|D|7|1K|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1L|8|@$E|1M|F|1N|G|W]]|9|@]|A|$]]|$1|X|3|Y|5|D|7|1O|8|@]|9|@]|A|$]]|$1|Z|3|10|5|D|7|1P|8|@$E|1Q|F|1R|G|H]]|9|@]|A|$]]|$1|11|3|12|5|6|7|1S|8|@]|9|@]|A|$]]|$1|13|3|14|5|6|7|1T|8|@$E|1U|F|1V|G|W]]|9|@]|A|$]]|$1|15|3|-4|5|6|7|1W|8|@]|9|@]|A|$]]]|16|$]]

I faced a similar situation:

<ol>
<li>logs were full with <code>parent transid verify failed on 109973766144 wanted 1823 found 1821</code></li>
<li>dmesg was full with <code>BTRFS info (device sda): no csum found for inode 16485445 start 73728</code> and <code>BTRFS warning (device sda): csum failed ino 16485465 off 36864 csum 2268363541 expected csum 0</code></li>
</ol>

configuration of my system

<ol start="3">
<li>NAS with 3 nfs shares</li>
<li>BTRFS file system</li>
<li>Rockstor Operating System</li>
<li>RAID 10 setup</li>
</ol>

additional information

<ol start="7">
<li>the btrfs mount became read only</li>
<li>btrfs-scrub failed with <code>ERROR: scrubbing /dev/md124p2 failed for device id 1: ret=-1, errno=5</code></li>
</ol>

I solved it by deleting the nfs export ie. from /etc/export/ and then remounting the volumes and voila everything became ok 

UPDATE 29 Jan 2018: after working for a few days it went back exactly to the same state

blocks|key|164620|text|类似/相同的问题如下：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|164621|parent+transid+verify+failed+on+29605888+wanted+50+found+46|offset|length|style|CODE|164622|对我来说，btrfs不再是可挂载的了，所以btrfs+scrub是没有选择的。而且我的/etc/exports也是空的。|164623|我试过btrfsck+--init-extent-tree+/dev/sda4，但仍然会出错。|164624|++++...
++++btrfs+check(main%2B0x82)[0x411ba2]
++++/lib64/libc.so.6(__libc_start_main%2B0xf5)[0x7f8210fab555]
++++btrfs+check[0x411ca8]
++++Aborted
++++#|code-block|syntax|javascript|164625|链接到屏幕截图(Updload不可能)：屏幕截图|164626|似乎唯一的解决方案是将数据还原到另一个磁盘。|164627|btrfs+restore+/dev/sda4+/mnt/anotherdisk/folder|164628|。|164629|entityMap|0|LINK|mutability|MUTABLE|url|https://previews.dropbox.com/p/thumb/AA49IrYkM3-Go31PE_Ic3psvDE94Fle-HKE0G3-fjMWEGsPgJiBgSwStAPYP6yS1ric8wmNkR3MsIUR1N2NTkD6ZpDzU6EhiKi9LhQE2Iu6l00ZSA8HaE3lWdTzRWZmtzTUDhSTT_j0sEh56DQa99fcbyXheoBVLpbD-GiriI_9z8OFBBETgN9isuohUpobZvBA6tx-xkefpWNwxOQ_X_X7hFKsMYkxK_Vb_TfnnkVCJq3R_AYsjR6AATLY2yb3aIZOzpzqECPWw2jxywQFIaVfgFEz9nHEkIjEGuFDlFMGKEM8hx_aOPogbCj7Zdo_5HIMXw7ZyEoLINrGi3yEbuSbZcADQzOaQ_J_SlB2FkViNlQ/p.png?fv_content=true&size_mode=5^0|0|0|1N|0|L|B|17|C|0|3|10|0|0|K|4|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|17|8|@$D|18|E|19|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|1A|8|@$D|1B|E|1C|F|G]|$D|1D|E|1E|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|1F|8|@$D|1G|E|1H|F|G]]|9|@]|A|$]]|$1|L|3|M|5|N|7|1I|8|@]|9|@]|A|$O|P]]|$1|Q|3|R|5|6|7|1J|8|@]|9|@$D|1K|E|1L|1|1M]]|A|$]]|$1|S|3|T|5|6|7|1N|8|@]|9|@]|A|$]]|$1|U|3|V|5|N|7|1O|8|@]|9|@]|A|$O|P]]|$1|W|3|X|5|6|7|1P|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|Z|$10|$5|11|12|13|A|$14|15]]]]

Similar/Same problem here:
<code>parent transid verify failed on 29605888 wanted 50 found 46</code>
<hr />
For me the btrfs is not mountable anymore so <code>btrfs scrub</code> is no option.
Also my <code>/etc/exports</code> are empty.
I tried <code>btrfsck --init-extent-tree /dev/sda4</code> but I still get errors.
<pre class="lang-sh prettyprint-override"><code> ...
 btrfs check(main+0x82)[0x411ba2]
 /lib64/libc.so.6(__libc_start_main+0xf5)[0x7f8210fab555]
 btrfs check[0x411ca8]
 Aborted
 #
</code></pre>
Link to Screenshot (Updload wasn't possible):
<a href="https://previews.dropbox.com/p/thumb/AA49IrYkM3-Go31PE_Ic3psvDE94Fle-HKE0G3-fjMWEGsPgJiBgSwStAPYP6yS1ric8wmNkR3MsIUR1N2NTkD6ZpDzU6EhiKi9LhQE2Iu6l00ZSA8HaE3lWdTzRWZmtzTUDhSTT_j0sEh56DQa99fcbyXheoBVLpbD-GiriI_9z8OFBBETgN9isuohUpobZvBA6tx-xkefpWNwxOQ_X_X7hFKsMYkxK_Vb_TfnnkVCJq3R_AYsjR6AATLY2yb3aIZOzpzqECPWw2jxywQFIaVfgFEz9nHEkIjEGuFDlFMGKEM8hx_aOPogbCj7Zdo_5HIMXw7ZyEoLINrGi3yEbuSbZcADQzOaQ_J_SlB2FkViNlQ/p.png?fv_content=true&amp;size_mode=5" rel="nofollow noreferrer">Screenshot</a>
It seems the only solution is to restore the data to another disk by
<pre><code>btrfs restore /dev/sda4 /mnt/anotherdisk/folder
</code></pre>
.

blocks|key|1801354|text|小心btrfs-零日志|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1801355|btrfs-零日志文档清楚地指出，它不是一个通用的工具：|offset|length|1801356|btrfs-零日志并不是一个通用的修复工具，，尽管许多人都相信它，并且在互联网上声明了这一点。你一般不需要用它。|blockquote|style|BOLD|1801357|这种工具只有一个用例:当您有BTRFS:+failed+to+read+log+tree日志时。|CODE|1801358|用usebackuproot修复父传递验证失败错误|1801359|3.2linux内核于2012年1月推出+recovery选项。然后，2016年5月推出了4.6版的“它被取代了+by+usebackuproot”。如果您感兴趣，也可以看到承诺。|1801360|文档清楚地解释了它所做的事情：|1801361|usebackuproot
nousebackuproot

++++(since:+4.6,+default:+off)

++++Enable+autorecovery+attempts+if+a+bad+tree+root+is+found+at+mount+time.
++++Currently+this+scans+a+backup+list+of+several+previous+tree+roots+and
++++tries+to+use+the+first+readable.+This+can+be+used+with+read-only+mounts+as+well.

++++Note:+This+option+has+replaced+recovery.|code-block|syntax|javascript|1801362|正式常见问题部分注记声明这是修复“父传递”错误的正确方法：|1801363|如何从“父传递验证失败”错误中恢复？
例如：
parent+transid+verify+failed+on+29360128+wanted+1486656+found+1486662
如果第二个数字(想要1486656和发现1486662)紧密地在一起(大约在20之间)，那么用
-o+ro,usebackuproot
也许能帮上忙。如果它在只读挂载中是成功的，那么在没有ro选项的情况下再试一次，以获得读写挂载。
--如果usebackuproot链接不工作，那么FS基本上是当前状态下的不可恢复的，使用当前的工具。您应该使用btrfs还原刷新备份，然后从备份恢复。|1801364|要使用的命令|1801365|这些命令只是Fedora安装上失败的btrfs磁盘的例子。用设备替换/dev/sda2，用挂载点替换/sysroot|1801366|首先在只读模式下尝试：|1801367|mount+-t+btrfs+-o+ro,usebackuproot+/dev/sda2+/sysroot|1801368|如果这有效，请在没有readonly命令的情况下再试一次：|1801369|mount+-t+btrfs+-o+usebackuproot+/dev/sda2+/sysroot|1801370|如果这样做有效，您应该能够引导您的Linux。|1801371|entityMap|0|LINK|mutability|MUTABLE|url|https://btrfs.wiki.kernel.org/index.php/Btrfs-zero-log|1|https://btrfs.wiki.kernel.org/index.php/Changelog#v3.2_.28Jan_2012.29|2|https://btrfs.wiki.kernel.org/index.php/Changelog#v4.6_.28May_2016.29|3|https://patchwork.kernel.org/project/linux-btrfs/patch/1453170184-22869-2-git-send-email-quwenruo@cn.fujitsu.com/#17472101|4|https://btrfs.wiki.kernel.org/index.php/Manpage/btrfs(5)|5|https://btrfs.wiki.kernel.org/index.php/FAQ#How_do_I_recover_from_a_.22parent_transid_verify_failed.22_error.3F^0|0|0|B|0|0|9|C|M|H|0|E|U|0|1|D|0|L|8|1O|D|A|A|1|1F|5|2|2F|2|3|0|0|2|4|0|0|0|A|5|0|N|1X|3X|J|57|2|5T|16|0|0|Y|9|1E|8|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1Z|8|@]|9|@$D|20|E|21|1|22]]|A|$]]|$1|F|3|G|5|H|7|23|8|@$D|24|E|25|I|J]|$D|26|E|27|I|J]]|9|@]|A|$]]|$1|K|3|L|5|6|7|28|8|@$D|29|E|2A|I|M]]|9|@]|A|$]]|$1|N|3|O|5|6|7|2B|8|@$D|2C|E|2D|I|M]]|9|@]|A|$]]|$1|P|3|Q|5|6|7|2E|8|@$D|2F|E|2G|I|M]|$D|2H|E|2I|I|M]]|9|@$D|2J|E|2K|1|2L]|$D|2M|E|2N|1|2O]|$D|2P|E|2Q|1|2R]]|A|$]]|$1|R|3|S|5|6|7|2S|8|@]|9|@$D|2T|E|2U|1|2V]]|A|$]]|$1|T|3|U|5|V|7|2W|8|@]|9|@]|A|$W|X]]|$1|Y|3|Z|5|6|7|2X|8|@]|9|@$D|2Y|E|2Z|1|30]]|A|$]]|$1|10|3|11|5|H|7|31|8|@$D|32|E|33|I|M]|$D|34|E|35|I|M]|$D|36|E|37|I|M]|$D|38|E|39|I|J]]|9|@]|A|$]]|$1|12|3|13|5|6|7|3A|8|@]|9|@]|A|$]]|$1|14|3|15|5|H|7|3B|8|@$D|3C|E|3D|I|M]|$D|3E|E|3F|I|M]]|9|@]|A|$]]|$1|16|3|17|5|6|7|3G|8|@]|9|@]|A|$]]|$1|18|3|19|5|V|7|3H|8|@]|9|@]|A|$W|X]]|$1|1A|3|1B|5|6|7|3I|8|@]|9|@]|A|$]]|$1|1C|3|1D|5|V|7|3J|8|@]|9|@]|A|$W|X]]|$1|1E|3|1F|5|6|7|3K|8|@]|9|@]|A|$]]|$1|1G|3|-4|5|6|7|3L|8|@]|9|@]|A|$]]]|1H|$1I|$5|1J|1K|1L|A|$1M|1N]]|1O|$5|1J|1K|1L|A|$1M|1P]]|1Q|$5|1J|1K|1L|A|$1M|1R]]|1S|$5|1J|1K|1L|A|$1M|1T]]|1U|$5|1J|1K|1L|A|$1M|1V]]|1W|$5|1J|1K|1L|A|$1M|1X]]]]

<h2>Beware of btrfs-zero-log</h2>
<a href="https://btrfs.wiki.kernel.org/index.php/Btrfs-zero-log" rel="noreferrer">btrfs-zero-log documentation</a> states clearly that it's not a generic tool to use:
<blockquote>
btrfs-zero-log is not a general fix-everything tool, despite what many people believe and state around the internet. You generally don't need to use it.
</blockquote>
There is only a use case for this tools: when you have <code>BTRFS: failed to read log tree</code> logs.
<h2>Fixing parent transid verify failed errors with <code>usebackuproot</code></h2>
The 3.2 Linux kernel <a href="https://btrfs.wiki.kernel.org/index.php/Changelog#v3.2_.28Jan_2012.29" rel="noreferrer">introduced in January 2012</a> the <code>recovery</code> option.
Then, in May 2016 with the 4.6 version, <a href="https://btrfs.wiki.kernel.org/index.php/Changelog#v4.6_.28May_2016.29" rel="noreferrer">it was superseded</a> by <code>usebackuproot</code>.
You can also see <a href="https://patchwork.kernel.org/project/linux-btrfs/patch/1453170184-22869-2-git-send-email-quwenruo@cn.fujitsu.com/#17472101" rel="noreferrer">the commit</a> if you're interested.
The <a href="https://btrfs.wiki.kernel.org/index.php/Manpage/btrfs(5)" rel="noreferrer">documentation</a> explain clearly what it does:
<pre><code>usebackuproot
nousebackuproot

 (since: 4.6, default: off)

 Enable autorecovery attempts if a bad tree root is found at mount time.
 Currently this scans a backup list of several previous tree roots and
 tries to use the first readable. This can be used with read-only mounts as well.

 Note: This option has replaced recovery.
</code></pre>
A <a href="https://btrfs.wiki.kernel.org/index.php/FAQ#How_do_I_recover_from_a_.22parent_transid_verify_failed.22_error.3F" rel="noreferrer">note in the official FAQ section</a> states that this is the right way to fix this &quot;parent transid&quot; error:
<blockquote>
How do I recover from a &quot;parent transid verify failed&quot; error?
For example:
<code>parent transid verify failed on 29360128 wanted 1486656 found 1486662</code>
If the second two numbers (wanted 1486656 and found 1486662) are close
together (within about 20 of each other), then mounting with
<code>-o ro,usebackuproot</code>
may help. If it's successful with a read-only mount, then try again
without the <code>ro</code> option, for a read-write mount.
If the usebackuproot doesn't work, then the FS is basically unrecoverable in its current state with current tools. You should use btrfs restore to refresh your backups, and then restore from them.
</blockquote>
<h2>Commands to use</h2>
<blockquote>
These commands are just example of a failed btrfs disk on a Fedora installation.
Replace <code>/dev/sda2</code> with your device and <code>/sysroot</code> with your mount point
</blockquote>
First try in read only mode:
<pre><code>mount -t btrfs -o ro,usebackuproot /dev/sda2 /sysroot
</code></pre>
If that works, try again without the readonly command:
<pre><code>mount -t btrfs -o usebackuproot /dev/sda2 /sysroot
</code></pre>
If this works, your should be able to boot your Linux.

blocks|key|1801432|text|首先运行以下命令：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1801433|sudo+btrfs+rescue+super-recover+-v+/dev/sda2|offset|length|style|CODE|1801434|如果它告诉您“所有的超级程序都是有效的，不需要恢复”，则需要运行以下命令来清除文件系统日志树：|1801435|sudo+btrfs+rescue+zero-log+/dev/sda2|1801436|现在您应该能够挂载您的Btrfs文件系统了。|1801437|entityMap^0|0|0|18|0|0|0|10|0|B|5|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@$D|R|E|S|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@$D|V|E|W|F|G]]|9|@]|A|$]]|$1|L|3|M|5|6|7|X|8|@$D|Y|E|Z|F|G]]|9|@]|A|$]]|$1|N|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|O|$]]

First run this command:
<code>sudo btrfs rescue super-recover -v /dev/sda2</code>
If it tells you “All supers are valid, no need to recover”, you need to run the following command to clear the filesystem log tree:
<code>sudo btrfs rescue zero-log /dev/sda2</code>
Now you should be able to mount your <code>Btrfs</code> file system.

<code>btrfs fi show</code> displays all btrfs file system but also a lot of errors like:

<blockquote>
 parent transid verify failed on 109973766144 wanted 1823 found 1821
</blockquote>

The filesystem can still be unmounted and remounted.

fix btrfs "btrfs parent transid verify failed on ..."

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

btrfs fi show显示所有btrfs文件系统，但也显示了许多错误，例如：父传递验证失败于109973766144 -1823年发现文件系统仍然可以卸载和重新安装。

问修正btrfs "btrfs父传递验证失败.“
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问修正btrfs "btrfs父传递验证失败.“EN