From: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
To: Daniel <daniel@wagners.name>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs-convert won't convert ext* - No valid Btrfs found on /dev/sdb1
Date: Fri, 11 Oct 2013 16:00:55 +0800 [thread overview]
Message-ID: <5257B037.6060303@cn.fujitsu.com> (raw)
In-Reply-To: <loom.20131011T095125-875@post.gmane.org>
Hello Daniel,
On 10/11/2013 03:52 PM, Daniel wrote:
> Hello Josef,
>
> Josef Bacik <jbacik <at> fusionio.com> writes:
>
>> On Thu, Sep 05, 2013 at 10:45:23AM -0500, Eric Sandeen wrote:
> [...]
>
>>> This was a regression around July 3; there was no regression test at
>>> the time.
>>>
>>> [615f2867854c186a37cb2e2e5a2e13e9ed4ab0df] Btrfs-progs: cleanup similar
> code in open_ctree_* and close_ctree
>>> broke it.
>>>
>>> Patches were sent to the list to fix it on July 17,
>>>
>>> https://patchwork.kernel.org/patch/2828820/
>>>
>>> but they haven't been merged into the main repo.
>>>
>>> I sent a regression test for it to the list on Aug 4, but nobody
>>> reviewed it, so it hasn't been merged into the test suite, either.
>>>
>>> Winning all around!
>> Alright, alright I'll review it, Jesus. ;),
> Is there any progress on this or can I help with solving this somehow?
This problem has been fixed , but it did not come into Chris's branch.
But it did come into david's integration branches.
http://github.com/kdave/btrfs-progs.git integration-20131008
Thanks,
Wang
>
>> Josef
> Daniel
>
> --
> 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
>
prev parent reply other threads:[~2013-10-11 8:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 14:43 btrfs-convert won't convert ext* - No valid Btrfs found on /dev/sdb1 Тимофей Титовец
2013-09-05 14:54 ` Hugo Mills
2013-09-05 15:06 ` Roman Mamedov
2013-09-05 15:30 ` Hugo Mills
2013-09-05 15:34 ` Roman Mamedov
2013-09-05 15:44 ` Hugo Mills
2013-09-05 15:45 ` Eric Sandeen
2013-09-05 18:44 ` Josef Bacik
2013-10-11 7:52 ` Daniel
2013-10-11 8:00 ` Wang Shilong [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=5257B037.6060303@cn.fujitsu.com \
--to=wangsl.fnst@cn.fujitsu.com \
--cc=daniel@wagners.name \
--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.