From: "Jörg Ebertz" <joerg.ebertz@gmx.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Tree-Checker-Error on vServer-Directory
Date: Thu, 21 May 2020 13:27:31 +0200 [thread overview]
Message-ID: <20200521112731.GC1838@ehud.gomer.local> (raw)
In-Reply-To: <f4ef60a7-df8b-71dc-5679-1628c0dda2ea@gmx.com>
On 2020-05-21, Qu Wenruo wrote:
> Btrfs check hasn't add such restrict check yet, and btrfs scrub doesn't
> check the tree contents.
>
> Furthermore, from the bit, it looks like a memory bitflip, and it is
> definitely caused in older kernels which doesn't has such comprehensive
> check.
Running rsync on the entire file system should trigger tree-checker, if
there are other damaged inodes, right?
> If it's a memory bitflip, it's highly recommended to run a full memtest
> to ensure your memory is OK.
I'll do that.
> To recover your data, it can be done by removing the offending inodes
> with older kernel.
>
> The inode can be located using the inode number provided in the dmesg.
sudo find / -inum 55495 -print
gave me
/vserver
To remove the inode, I run
sudo mkdir /vserver2
sudo cp -a --reflink /vserver /vserver2
sudo rm /vserver
sudo mv /vserver2 /vserver
correct?
Joerg
prev parent reply other threads:[~2020-05-21 11:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 15:54 Tree-Checker-Error on vServer-Directory joerg.ebertz
2020-05-20 22:50 ` Qu Wenruo
2020-05-21 11:27 ` Jörg Ebertz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200521112731.GC1838@ehud.gomer.local \
--to=joerg.ebertz@gmx.net \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).