All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Eisserer <linuxhippy@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Btrfsck errors (fs tree 565 refs 125 not found) - how serious
Date: Mon, 27 May 2013 02:07:06 +0200	[thread overview]
Message-ID: <CAFvQSYShdQL_pZB12=Xt7dg+yLt0NNCW+WTyOXgic3SbFDy69w@mail.gmail.com> (raw)

Hi,

For about 3 weeks I've been using btrfs on my desktop machine, using
the snapshot-functionality quite a lot.

Today I ran btrfsck and got about ~10MB of output which looks like:

fs tree 565 refs 125 not found
	unresolved ref root 807 dir 813347 index 277 namelen 39 name
snapshot_1368273601_2013-05-11_14:00:01 error 600
	unresolved ref root 808 dir 813347 index 277 namelen 39 name
snapshot_1368273601_2013-05-11_14:00:01 error 600
.......

fs tree 566 refs 125 not found
	unresolved ref root 807 dir 813347 index 278 namelen 39 name
snapshot_1368274201_2013-05-11_14:10:01 error 600
	unresolved ref root 808 dir 813347 index 278 namelen 39 name
snapshot_1368274201_2013-05-11_14:10:01 error 600
......


while the log contained a lot of different values for "fs tree", the
refs which were not found stays fairly constant:

refs: 125, 397, 398, 406, 407, 420

How serious are those issues, should I be worried?
Would it help if I find ways to reproduce this behaviour on a fresh
btrfs filesystem?

Thank you in advance, Clemens

             reply	other threads:[~2013-05-27  0:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-27  0:07 Clemens Eisserer [this message]
2013-05-30 18:06 ` Btrfsck errors (fs tree 565 refs 125 not found) - how serious Clemens Eisserer
2013-05-30 18:55   ` Josef Bacik
2013-05-30 19:36     ` Clemens Eisserer
2013-05-31 20:43       ` Clemens Eisserer

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='CAFvQSYShdQL_pZB12=Xt7dg+yLt0NNCW+WTyOXgic3SbFDy69w@mail.gmail.com' \
    --to=linuxhippy@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.