All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lakshmipathi.G" <lakshmipathi.g@gmail.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: btrfs <linux-btrfs@vger.kernel.org>, David Sterba <dsterba@suse.com>
Subject: Re: misc/021-image-multi-devices fails on latest btrfs-devel/misc-next
Date: Sun, 26 Nov 2017 17:06:30 +0530	[thread overview]
Message-ID: <CAKuJGC8C3-yZG9AwBfXQAPHQUrub7W6BfrdrEGwLuahbXYVw0A@mail.gmail.com> (raw)
In-Reply-To: <CAKuJGC_aE4bHsp6pOBibFsMa_5inO9sgb-djx5Dc903-sR3=Nw@mail.gmail.com>

Hi Qu,

I checked with David, Seems like his github/repo.or.cz repo has latest
dev patches
before pushing them into kernel.org repo.

--
With the help of 'git bisect', managed to debug this issue further.
With this patch[1]
applied we are running into this issue.

https://asciinema.org/a/OMLXpd69iHaej0Xfsrr2ihKiP

[1] btrfs: factor __btrfs_open_devices() to create btrfs_open_one_device()
https://github.com/kdave/btrfs-devel/commit/25908a59bb5c54f896c646ed3a1f73b2727ad9b5

----
Cheers,
Lakshmipathi.G
http://www.giis.co.in http://www.webminal.org


On Fri, Nov 24, 2017 at 5:35 PM, Lakshmipathi.G
<lakshmipathi.g@gmail.com> 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.
>
> Okay, I didn't know that one, let me checkout his git.kernel.org branch and
> check the results there.
>
>>
>> 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.
>>
>
> Yes. something strange going on. I use the same kernel config
> for misc-next, 4.14 and 4.14.2 - issue happens only with
> misc-next, as you mentioned it may not be up-to-date.
>
>
> ----
> Cheers,
> Lakshmipathi.G
> http://www.giis.co.in http://www.webminal.org

      reply	other threads:[~2017-11-26 11:37 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
2017-11-24 12:05                       ` Lakshmipathi.G
2017-11-26 11:36                         ` Lakshmipathi.G [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=CAKuJGC8C3-yZG9AwBfXQAPHQUrub7W6BfrdrEGwLuahbXYVw0A@mail.gmail.com \
    --to=lakshmipathi.g@gmail.com \
    --cc=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.com \
    /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.