From: Liu Bo <liubo2009@cn.fujitsu.com>
To: dima <dolenin@parallels.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: unresolved ref root error
Date: Tue, 18 Oct 2011 09:15:16 +0800 [thread overview]
Message-ID: <4E9CD324.80504@cn.fujitsu.com> (raw)
In-Reply-To: <loom.20111016T032429-296@post.gmane.org>
On 10/16/2011 09:37 AM, dima wrote:
> Hello,
>
> On a newly created filesystem with btrfs-progs-git-20111009 and the 3.1.0-rc8
> kernel I am getting the following error when doing btrfsck after main OS
> installation
>
> fs tree 256 refs 2
> unresolved ref root 256 dir 256 index 2 namelen 8 name __active error 600
> found 4215058432 bytes used err is 1
> total csum bytes: 3962760
> total tree bytes: 157192192
> total fs tree bytes: 146976768
> btree space waste bytes: 45236856
> file data blocks allocated: 4123439104
> referenced 4056010752
> Btrfs v0.19-35-g1b444cd-dirty
>
> 256 is the subvolume for /
> [root@yukikaze ~]# btrfs subvol list /
> ID 256 top level 5 path __active
> ID 257 top level 5 path __home
>
> Should I be concerned with this error?
>
Don't worry, this is a known bug of btrfsck's refs check, and just btrfsck,
it does no harm to btrfs.
thanks,
liubo
> I saw a similar question here
> http://comments.gmane.org/gmane.comp.file-systems.btrfs/12455
> but no hints were provided for the reason of the error.
>
> Any info is appreciated.
> thanks
> ~dima
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2011-10-18 1:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-16 1:37 unresolved ref root error dima
2011-10-18 1:15 ` Liu Bo [this message]
2011-10-18 3:14 ` dima
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=4E9CD324.80504@cn.fujitsu.com \
--to=liubo2009@cn.fujitsu.com \
--cc=dolenin@parallels.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.