From: Michael Welsh Duggan <mwd@md5i.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs-progs: receive: fix the case that we can not find subvolume
Date: Wed, 18 Dec 2013 15:57:36 -0500 [thread overview]
Message-ID: <87txe5ri67.fsf@maru2.md5i.com> (raw)
In-Reply-To: 52B12C85.6090503@cn.fujitsu.com
Wang Shilong <wangsl.fnst@cn.fujitsu.com> writes:
> On 12/18/2013 12:06 PM, Michael Welsh Duggan wrote:
>> Wang Shilong <wangsl.fnst@cn.fujitsu.com> writes:
>>
>>> It seems that you use older kernel version but use the latest
>>> btrfs-progs, new btrfs-progs use uuid tree to search but
>>> this tree did not exist yet.
>>>
>>> Can you try to upgrade your kernel?
>> What version is necessary? (I am currently on 3.11.10.)
> 3.12 is ok, btw, can you run for 3.11.10
>
> #dmesg
>
> Let's see if it output somthing like:
>
> btrfs: can not found root: 9
Indeed.
$ dmesg | grep "root 9"
[305770.945287] could not find root 9
[305770.945300] could not find root 9
[305770.945369] could not find root 9
[305770.945398] could not find root 9
[305915.405421] could not find root 9
[305915.405483] could not find root 9
[305962.927150] could not find root 9
[305962.927222] could not find root 9
[399096.924559] could not find root 9
[399096.924617] could not find root 9
[399195.585768] could not find root 9
[399195.585823] could not find root 9
Looks like I'll be rebooting to a new kernel when I get home tonight.
--
Michael Welsh Duggan
(md5i@md5i.com)
next prev parent reply other threads:[~2013-12-18 20:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 9:13 [PATCH] Btrfs-progs: receive: fix the case that we can not find subvolume Wang Shilong
2013-12-17 15:09 ` David Sterba
2013-12-17 15:27 ` Wang Shilong
2013-12-17 15:40 ` Michael Welsh Duggan
2013-12-18 2:55 ` Miao Xie
2013-12-18 3:29 ` Michael Welsh Duggan
2013-12-18 3:54 ` Wang Shilong
2013-12-18 4:06 ` Michael Welsh Duggan
2013-12-18 5:03 ` Wang Shilong
2013-12-18 20:57 ` Michael Welsh Duggan [this message]
2013-12-20 2:33 ` Michael Welsh Duggan
2013-12-19 16:48 ` David Sterba
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=87txe5ri67.fsf@maru2.md5i.com \
--to=mwd@md5i.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