Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: dsterba@suse.cz, Filipe Manana <fdmanana@kernel.org>
Cc: linux-btrfs@vger.kernel.org, dsterba@suse.com,
	aromosan@gmail.com, bernd.feige@gmx.net,
	CHECK_1234543212345@protonmail.com, stable@vger.kernel.org
Subject: Re: [PATCH v2] btrfs: do not skip re-registration for the mounted device
Date: Wed, 21 Feb 2024 22:09:59 +0530	[thread overview]
Message-ID: <bdaa5790-56d8-4490-9eab-9a47e4926661@oracle.com> (raw)
In-Reply-To: <20240220181236.GF355@suse.cz>

On 2/20/24 23:42, David Sterba wrote:
> On Tue, Feb 20, 2024 at 02:08:00PM +0000, Filipe Manana wrote:
>> On Wed, Feb 14, 2024 at 7:17 AM David Sterba <dsterba@suse.cz> wrote:
>>> On Tue, Feb 13, 2024 at 09:13:56AM +0800, Anand Jain wrote:
>>> https://btrfs.readthedocs.io/en/latest/dev/Developer-s-FAQ.html#ordering
>>
>> So this introduces a regression.
>>
>> $ ./check btrfs/14[6-9] btrfs/15[8-9]
> 
> Thanks, with this I can reproduce it and have some ideas what could go
> wrong.


Thanks indeed.

I see some error during mkfs.

ERROR: /dev/sdb1 is smaller than requested size, expected 1073741824, 
found 766509056

-Anand



  reply	other threads:[~2024-02-21 16:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13  1:13 [PATCH v2] btrfs: do not skip re-registration for the mounted device Anand Jain
2024-02-14  7:16 ` David Sterba
2024-02-20 14:08   ` Filipe Manana
2024-02-20 18:12     ` David Sterba
2024-02-21 16:39       ` Anand Jain [this message]
2024-02-21 17:03         ` Anand Jain
2024-02-21 21:49         ` David Sterba
2024-02-22  2:45           ` Anand Jain
2024-02-22 21:07             ` Anand Jain
2024-03-07  4:13     ` 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=bdaa5790-56d8-4490-9eab-9a47e4926661@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=CHECK_1234543212345@protonmail.com \
    --cc=aromosan@gmail.com \
    --cc=bernd.feige@gmx.net \
    --cc=dsterba@suse.com \
    --cc=dsterba@suse.cz \
    --cc=fdmanana@kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=stable@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