linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: fdmanana@gmail.com, dsterba@suse.cz,
	Anand Jain <anand.jain@oracle.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs_progs: mkfs: match devid order to the stripe index
Date: Wed, 11 Dec 2019 09:45:09 +0800	[thread overview]
Message-ID: <3a3acd6a-ed5b-bc35-58aa-f76f7704a240@gmx.com> (raw)
In-Reply-To: <CAL3q7H7nbp_kmeEZpRL7KpwhXSA6=QCcwzXT-f0szrwRmW-ohw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1469 bytes --]



On 2019/12/10 下午11:42, Filipe Manana wrote:
> On Thu, Sep 12, 2019 at 10:39 PM David Sterba <dsterba@suse.cz> wrote:
>>
>> On Tue, Sep 03, 2019 at 02:06:03PM +0200, David Sterba wrote:
>>> On Mon, Sep 02, 2019 at 06:22:30PM +0200, David Sterba wrote:
>>>> On Mon, Sep 02, 2019 at 04:01:56PM +0800, Anand Jain wrote:
>>>>>
>>>>> David,
>>>>>
>>>>>   I don't see this patch is integrated. Can you please integrated this
>>>>> patch thanks.
>>>>
>>>> I don't know why but the patch got lost somewhere, adding to devel
>>>> again.
>>>
>>> Not lost, but dropped, misc-tests/021 fails. So dropped again, please
>>> fix it and test before posting again. Thanks.
>>
>> With the test misc/021 updated, this patch has been added to devel.
>> Thanks.
> 
> So having updated my local btrfs-progs from v5.2.2 to 5.4, I started
> getting 4 test cases from fstests failing:

Was running with btrfs-progs v5.3.1 before, so not hit the bug...
(And some notrun due to missing make_fail_request config)

> 
> Am I the only one getting this? It's been a while and I can't have
> been the only one running fstests with progs 5.3+.
> Is there any fix around for btrfs-progs I missed in mailing list (with
> devel branch the tests fail as well), or a plan to update the tests?

I'll look into the test case to fix them, since most of them are just
bad golden output, not a big deal to handle.

Thanks for the report,
Qu

> 
> thanks
> 
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-12-11  1:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-28  2:26 [PATCH] btrfs_progs: mkfs: match devid order to the stripe index Anand Jain
2019-06-28  2:44 ` Qu Wenruo
2019-06-28  3:28   ` Anand Jain
2019-06-28  6:01     ` Qu Wenruo
2019-07-03 13:21 ` David Sterba
2019-08-27  2:02   ` Anand Jain
2019-09-02  8:01     ` Anand Jain
2019-09-02 16:22       ` David Sterba
2019-09-03 12:06         ` David Sterba
2019-09-04 11:10           ` Anand Jain
2019-09-12 17:54           ` David Sterba
2019-12-10 15:42             ` Filipe Manana
2019-12-11  1:45               ` Qu Wenruo [this message]
2019-12-11  8:58                 ` Filipe Manana
2019-09-03 10:46 ` Johannes Thumshirn
2019-09-04 12:54   ` [PATCH] btrfs: misc-tests-021 fix restore overlapped on disk's stale data Anand Jain
2019-09-04 13:29   ` [PATCH Fix-title-prefix] btrfs-progs: " Anand Jain
2019-09-04 14:05     ` Johannes Thumshirn
2019-09-04 14:06     ` Nikolay Borisov
2019-09-10  7:43     ` Anand Jain
2019-09-12 17:49     ` David Sterba
2019-09-10  7:37 ` [PATCH] btrfs_progs: mkfs: match devid order to the stripe index Anand Jain

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=3a3acd6a-ed5b-bc35-58aa-f76f7704a240@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=anand.jain@oracle.com \
    --cc=dsterba@suse.cz \
    --cc=fdmanana@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).