From: "Yan, Zheng " <yanzheng@21cn.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Kernel BUG in tree-log.c on mount
Date: Fri, 16 Oct 2009 11:11:14 +0800 [thread overview]
Message-ID: <3d0408630910152011w15fbbcdbj8f324b2c943cc3d7@mail.gmail.com> (raw)
In-Reply-To: <cb81ffa90910151940y426ff7d7wa1e545102a17de69@mail.gmail.com>
n Fri, Oct 16, 2009 at 10:40 AM, David Pflug <dtpflug@gmail.com> wrote:
> On Thu, Oct 15, 2009 at 10:07 PM, Yan, Zheng <yanzheng@21cn.com> wrote:
>> On Thu, Oct 15, 2009 at 11:48 AM, David Pflug <dtpflug@gmail.com> wrote:
>>> I don't know if there's any useful data in this dump, for you guys. I
>>> can get you the output of btrfs-debug-tree as well, if it'd be
>>> helpful.
>>
>> We never saw this bug before, please send the output of btrfs-debug-tree.
> http://tpflug.name/btrfs_debug_tree.txt.bz2
log tree key (TREE_LOG ROOT_ITEM 5)
leaf 1453862912 items 9 free space 2349 generation 4803 owner 1
fs uuid a369f9c7-c3c4-40bd-a191-907f79f51205
chunk uuid 20df5ed7-f708-437d-b297-a4372ca67a7d
item 0 key (EXTENT_TREE ROOT_ITEM 0) itemoff 3756 itemsize 239
root data bytenr 1450123264 level 2 dirid 0 refs 1
item 1 key (DEV_TREE ROOT_ITEM 0) itemoff 3517 itemsize 239
root data bytenr 1517395968 level 0 dirid 0 refs 1
item 2 key (FS_TREE INODE_REF 6) itemoff 3500 itemsize 17
inode ref index 0 namelen 7 name: default
item 3 key (FS_TREE ROOT_ITEM 0) itemoff 3261 itemsize 239
root data bytenr 1449054208 level 3 dirid 256 refs 1
item 4 key (ROOT_TREE_DIR INODE_ITEM 0) itemoff 3101 itemsize 160
inode generation 4 size 0 block group 0 mode 40555 links 1
item 5 key (ROOT_TREE_DIR INODE_REF 6) itemoff 3089 itemsize 12
inode ref index 0 namelen 2 name: ..
item 6 key (ROOT_TREE_DIR DIR_ITEM 2378154706) itemoff 3052 itemsize 37
location key (FS_TREE ROOT_ITEM 18446744073709551615) type 2
namelen 7 datalen 0 name: default
item 7 key (CSUM_TREE ROOT_ITEM 0) itemoff 2813 itemsize 239
root data bytenr 1449447424 level 2 dirid 0 refs 1
item 8 key (DATA_RELOC_TREE ROOT_ITEM 0) itemoff 2574 itemsize 239
root data bytenr 29380608 level 0 dirid 256 refs 1
The contents of log tree is the same as root tree. I guess the block
group caching bug is the cause.
Yan, Zheng
prev parent reply other threads:[~2009-10-16 3:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 3:48 Kernel BUG in tree-log.c on mount David Pflug
2009-10-15 16:48 ` David Pflug
2009-10-15 18:39 ` Josef Bacik
2009-10-16 2:07 ` Yan, Zheng
[not found] ` <cb81ffa90910151940y426ff7d7wa1e545102a17de69@mail.gmail.com>
2009-10-16 3:11 ` Yan, Zheng [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=3d0408630910152011w15fbbcdbj8f324b2c943cc3d7@mail.gmail.com \
--to=yanzheng@21cn.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