From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: "Lakshmipathi.G" <lakshmipathi.g@gmail.com>
Cc: btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: misc/021-image-multi-devices fails on latest btrfs-devel/misc-next
Date: Fri, 24 Nov 2017 19:50:19 +0800 [thread overview]
Message-ID: <9932efee-4784-60db-114f-a6ce3ed01b7c@gmx.com> (raw)
In-Reply-To: <CAKuJGC930Nm4pNqA+xH5HRbx0pWBKR4KXnS32hP+NYSdvO7arA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1683 bytes --]
On 2017年11月24日 19:42, Lakshmipathi.G wrote:
>>
>> To make it clear, what kernel config and commit are you using when the
>> test fails?
>>
> When I use attached kernel config along with tar from misc-next branch
> (wget https://github.com/kdave/btrfs-devel/archive/misc-next.zip) this
> issue happens.
BTW, David seems to update his branch more often in his git.kernel.org
branch than github.
So it's possible that the branch from github is out dated.
>
>> In my test, if I use the david/for-4.15 branch, it will fails to umount
>> the fs, due to the known bug if you enabled
>> CONFIG_BTRFS_FS_CHECK_INTEGRITY (you reported it first).
>> And for any upstream kernel version like v4.14-rc7 or v4.14, not problem
>> at all.
>>
> Here's btrfs related config. I checked with 4.14.2 it worked fine there too.
>
> The issue happens with v4.14-rc7, can you check with above config
> file and zip file(misc-next.zip)?
>
> $ cat kernel.config | grep "BTRFS"
> CONFIG_BTRFS_FS=y
> CONFIG_BTRFS_FS_POSIX_ACL=y
> CONFIG_BTRFS_FS_CHECK_INTEGRITY=n
> CONFIG_BTRFS_FS_RUN_SANITY_TESTS=n
> CONFIG_BTRFS_DEBUG=y
> CONFIG_BTRFS_ASSERT=y
> CONFIG_BTRFS_FS_REF_VERIFY=y
For v4.14-rc7, even I enabled all the btrfs related configs, I still
can't reproduce it.
------
$ zcat /proc/config.gz | grep BTRFS
CONFIG_BTRFS_FS=m
CONFIG_BTRFS_FS_POSIX_ACL=y
CONFIG_BTRFS_FS_CHECK_INTEGRITY=y
CONFIG_BTRFS_FS_RUN_SANITY_TESTS=y
CONFIG_BTRFS_DEBUG=y
CONFIG_BTRFS_ASSERT=y
------
So there is something strange happened.
Thanks,
Qu
>
> thanks!
>
> ----
> Cheers,
> Lakshmipathi.G
> http://www.giis.co.in http://www.webminal.org
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 520 bytes --]
next prev parent reply other threads:[~2017-11-24 11:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-18 7:29 misc/021-image-multi-devices fails on latest btrfs-devel/misc-next Lakshmipathi.G
2017-11-23 3:16 ` Lakshmipathi.G
2017-11-24 1:18 ` Qu Wenruo
2017-11-24 4:25 ` Lakshmipathi.G
2017-11-24 7:47 ` Lakshmipathi.G
2017-11-24 8:06 ` Qu Wenruo
2017-11-24 8:20 ` Lakshmipathi.G
2017-11-24 8:29 ` Qu Wenruo
2017-11-24 10:15 ` Lakshmipathi.G
2017-11-24 11:22 ` Qu Wenruo
[not found] ` <CAKuJGC930Nm4pNqA+xH5HRbx0pWBKR4KXnS32hP+NYSdvO7arA@mail.gmail.com>
2017-11-24 11:50 ` Qu Wenruo [this message]
2017-11-24 12:05 ` Lakshmipathi.G
2017-11-26 11:36 ` Lakshmipathi.G
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=9932efee-4784-60db-114f-a6ce3ed01b7c@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=lakshmipathi.g@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).