linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <ckulkarnilinux@gmail.com>
To: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
	linux-block@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org, Bart Van Assche <bvanassche@acm.org>,
	Naohiro Aota <naohiro.aota@wdc.com>
Subject: Re: [PATCH blktests] zbd/009: increase max open zones limit to 16
Date: Mon, 25 Aug 2025 17:43:52 -0700	[thread overview]
Message-ID: <7be35af0-d249-4910-8f67-309e111f8c08@gmail.com> (raw)
In-Reply-To: <20250826002720.12222-1-shinichiro.kawasaki@wdc.com>

On 8/25/25 17:27, Shin'ichiro Kawasaki wrote:
> The kernel commit 04147d8394e8 ("btrfs: zoned: limit active zones to
> max_open_zones") introduced in kernel version v6.17-rc3 caused the
> zbd/009 test case to hang during execution. The hang happens because
> zoned btrfs requires the maximum active zones limit of zoned block
> devices to be at least 11 or greater. The kernel commit applies this
> same requirement to the maximum open zones limit also.
>
> However, by default, the maximum open zones limit for zoned scsi_debug
> devices is 8. The test case zbd/009 creates a scsi_debug device with
> this limit and set up zoned btrfs. Thereby it violates the 11-zones
> requirement, which resulted in the hang.
>
> To avoid the hang, increase the max open zones limit of the scsi_debug
> device from the default value 8 to 16.
>
> Suggested-by: Naohiro Aota<naohiro.aota@wdc.com>
> Signed-off-by: Shin'ichiro Kawasaki<shinichiro.kawasaki@wdc.com>

Looks good.

Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>

-ck


  reply	other threads:[~2025-08-26  0:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-26  0:27 [PATCH blktests] zbd/009: increase max open zones limit to 16 Shin'ichiro Kawasaki
2025-08-26  0:43 ` Chaitanya Kulkarni [this message]
2025-08-31 11:11 ` Shinichiro Kawasaki

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=7be35af0-d249-4910-8f67-309e111f8c08@gmail.com \
    --to=ckulkarnilinux@gmail.com \
    --cc=bvanassche@acm.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=naohiro.aota@wdc.com \
    --cc=shinichiro.kawasaki@wdc.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;
as well as URLs for NNTP newsgroup(s).