From: Anand Jain <anand.jain@oracle.com>
To: fdmanana@gmail.com, Nikolay Borisov <nborisov@suse.com>
Cc: fstests <fstests@vger.kernel.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs/154: test for device dynamic rescan
Date: Sun, 21 Oct 2018 22:13:03 +0800 [thread overview]
Message-ID: <184cb50c-1504-039b-6792-b5a710296ded@oracle.com> (raw)
In-Reply-To: <CAL3q7H7inq5UCgihaP8i+9NOGiSvDGc6ndphMyuONc6OTJFtiw@mail.gmail.com>
On 10/21/2018 05:31 PM, Filipe Manana wrote:
> On Sun, Oct 21, 2018 at 10:20 AM Nikolay Borisov <nborisov@suse.com> wrote:
>>
>>
>>
>> On 21.10.2018 10:16, Filipe Manana wrote:
>>> On Mon, Nov 13, 2017 at 2:26 AM Anand Jain <anand.jain@oracle.com> wrote:
>>>>
>>>> Make sure missing device is included in the alloc list when it is
>>>> scanned on a mounted FS.
>>>>
>>>> This test case needs btrfs kernel patch which is in the ML
>>>> [PATCH] btrfs: handle dynamically reappearing missing device
>>>> Without the kernel patch, the test will run, but reports as
>>>> failed, as the device scanned won't appear in the alloc_list.
>>>
>>> So that patch was never merged, at least not with that subject.
>>> What happened?
The contending patch at V5 (with fixed comments as received) was
working fine at the then latest kernel version, now its out dated,
and I am not sure where to invest my time, it will be better to
have David's comment, if he has any concern on the idea/approach
in general. I am ok to revive the patch.
>> https://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git/tree/tests/btrfs/154
>>
>> In my testing of misc-next this test has been failing for me.
Don't bother about that patch I am sure its not good on the current
kernel.
> recent hole punch
> test, that doesn't have a corresponding kernel fix.
Hole punching kernel patch, fixes a corner case, I tried but failed.
Until my current priority list recedes I won't be able to look into
it again. If you would like to pick this up pls go ahead. I think it
will easy for you.
Lastly, I think its a good idea to record the current known limitation
as a test cases, even if it fails, in that way it gets documented.
Thanks, Anand
prev parent reply other threads:[~2018-10-21 22:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 2:25 [PATCH] btrfs/154: test for device dynamic rescan Anand Jain
2017-11-14 12:12 ` Eryu Guan
2017-11-15 3:04 ` Anand Jain
2017-11-15 3:05 ` [PATCH v2] " Anand Jain
2017-11-15 6:47 ` Eryu Guan
2017-11-15 10:13 ` Anand Jain
2018-10-21 9:16 ` [PATCH] " Filipe Manana
2018-10-21 9:20 ` Nikolay Borisov
2018-10-21 9:31 ` Filipe Manana
2018-10-21 14:13 ` Anand Jain [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=184cb50c-1504-039b-6792-b5a710296ded@oracle.com \
--to=anand.jain@oracle.com \
--cc=fdmanana@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox