From: Hugo Mills <hugo@carfax.org.uk>
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 21:31:02 +0000 [thread overview]
Message-ID: <20160201213102.GC8313@carfax.org.uk> (raw)
In-Reply-To: <56AFC213.8040501@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1391 bytes --]
On Mon, Feb 01, 2016 at 03:37:39PM -0500, Austin S. Hemmelgarn wrote:
> On 2016-02-01 15:21, Hugo Mills wrote:
> >On Mon, Feb 01, 2016 at 02:44:24PM -0500, Austin S. Hemmelgarn 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?
> >
> > Yes, those are errors I'd expect btrfs check --repair to handle
> >properly.
> >
> Out of curiosity, do you happen to know if this is how btrfs check
> reports orphaned inodes, or is this something else entirely?
I don't know, sorry.
Hugo.
--
Hugo Mills | We teach people management skills by examining
hugo@... carfax.org.uk | characters in Shakespeare. You could look at
http://carfax.org.uk/ | Claudius's crisis management techniques, for
PGP: E2AB1DE4 | example. Richard Smith-Jones, Slings and Arrows
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2016-02-01 21:31 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 [this message]
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
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=20160201213102.GC8313@carfax.org.uk \
--to=hugo@carfax.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.