From: Chris Murphy <lists@colorremedies.com>
To: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Question about a specific error.
Date: Mon, 1 Feb 2016 13:27:50 -0700 [thread overview]
Message-ID: <CAJCQCtQKPY537mZS0UVNzFQjCCVi6ik643wjssDnxGKiojcNzg@mail.gmail.com> (raw)
In-Reply-To: <56AFB598.2020307@gmail.com>
On Mon, Feb 1, 2016 at 12:44 PM, Austin S. Hemmelgarn
<ahferroin7@gmail.com> wrote:
> In the process of trying to debug issues I'm having on one of my
> systems with a new kernel version, I decided to do a dry run check on
> the root filesystem. 'btrfs check' returned a bunch of lines like:
>
> root 257 inode XXXXXX errors 2000, link count wrong
> unresolved ref dir YYYYY index 53 namelen 3 name LOG filetype 0 errors 3, no dir item, no dir index
>
> I got about 20 messages like this with varying values for everything
> except the filetype and error counts. Based on what I can tell, these
> look like orphaned inodex, but I'm not certain.
> Is it safe to tell BTRFS to try and fix these errors?
Is it consistent between boots? I have a system with SSD where if I
boot with rd.break=pre-mount, and run btrfs check, I sometimes get a
long string of similar messages. But upon reboot they don't happen
anymore.
--
Chris Murphy
next prev parent reply other threads:[~2016-02-01 20:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 19:44 Question about a specific error Austin S. Hemmelgarn
2016-02-01 20:21 ` Hugo Mills
2016-02-01 20:37 ` Austin S. Hemmelgarn
2016-02-01 21:31 ` Hugo Mills
2016-02-02 13:00 ` Austin S. Hemmelgarn
2016-02-03 21:17 ` Chris Murphy
2016-02-03 21:27 ` Hugo Mills
2016-02-04 12:18 ` Austin S. Hemmelgarn
2016-02-04 10:56 ` Duncan
2016-02-01 20:27 ` Chris Murphy [this message]
2016-02-01 20:35 ` Austin S. Hemmelgarn
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=CAJCQCtQKPY537mZS0UVNzFQjCCVi6ik643wjssDnxGKiojcNzg@mail.gmail.com \
--to=lists@colorremedies.com \
--cc=ahferroin7@gmail.com \
--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).