Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: "Martin Škoda" <mar.skoda@gmail.com>
To: johannes.thumshirn@wdc.com
Cc: a2jphilipp@gmail.com, dsterba@suse.com,
	linux-btrfs@vger.kernel.org, naohiro.aota@wdc.com,
	zhudongjiang@fygo.io
Subject: Re: [PATCH v3] btrfs: zoned: don't release active zone reservations for conventional zones
Date: Fri, 13 Nov 2026 17:16:50 +0100	[thread overview]
Message-ID: <e3261fe5-4b98-47e6-ae66-d4af05caa621@gmail.com> (raw)
In-Reply-To: <20261110080932.1205332-1-johannes.thumshirn@wdc.com>

Hello,

I would like to report another case of Btrfs zoned filesystem failures 
on a Western Digital host-managed SMR drive. My symptoms appear very 
similar to those being discussed in this thread.

*System configuration:*

  *

    Distribution: Ubuntu Server 26.04 LTS

  *

    Affected drive: WDC WSH722870ALE604, 27 TB, host-managed SMR

  *

    Filesystem: Btrfs zoned, single-device filesystem

  *

    Zone size: 256 MiB

  *

    Kernel versions tested: Ubuntu 7.0.0-34-generic and 7.0.0-42-generic

*Observed failures:*

On kernel 7.0.0-42, writing large media files repeatedly produced:

|BTRFS error (device sdg): cow_file_range failed ...: -28 BTRFS error 
(device sdg): failed to run delalloc range ...: -28|

These errors occurred despite several TiB of free space being reported.

On kernel 7.0.0-34, I also observed a transaction abort on November 7, 2026:

|BTRFS error (device sdg): error while writing out transaction: -11 
BTRFS warning (device sdg): Skipping commit of aborted transaction. 
BTRFS: Transaction aborted (error -11) BTRFS: error (device sdg state A) 
in cleanup_transaction:2060: errno=-11 unknown BTRFS info (device sdg 
state EA): forced readonly|

At that time, Btrfs filesystem usage reported:

|Device size: 24.56 TiB Device unallocated: 10.65 TiB Device zone 
unusable: 251.31 GiB Free (estimated): 10.86 TiB|

All Btrfs device error counters were zero, including write, read, flush, 
corruption and generation errors.

Both dynamic and periodic reclaim were disabled, and the reclaim 
counters were zero.

The issue has occurred repeatedly. The filesystem becomes read-only 
after the transaction failure, and normal write operations cannot continue.

I have currently disabled writes to this drive through mergerfs to avoid 
further data loss. The filesystem contains important data without a 
complete backup, so I cannot safely test experimental kernels or perform 
destructive recovery procedures.

Could you confirm whether these symptoms match the active-zone 
reservation/accounting issue addressed by this patch series? If so, is 
there a recommended stable kernel or an Ubuntu backport that includes 
the necessary fixes?

I can provide additional kernel logs, filesystem statistics and 
read-only diagnostic information if useful. I would also be interested 
to know which fixes are planned for stable kernels and whether a 
backport to Ubuntu's 7.0 kernel series is possible.

Thank you for your work on Btrfs zoned support.

Martin Škoda


  parent reply	other threads:[~2026-11-13 16:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-10  8:09 [PATCH v3] btrfs: zoned: don't release active zone reservations for conventional zones Johannes Thumshirn
2026-11-10 15:08 ` Jochen Philipp
2026-11-13 10:09   ` Dongjiang Zhu
2026-11-13 10:14     ` Jochen Philipp
2026-11-13 12:40       ` Jochen Philipp
2026-11-13 14:00         ` Jochen Philipp
2026-11-13 14:45           ` Johannes Thumshirn
2026-11-13 14:55             ` Jochen Philipp
2026-11-13 16:16 ` Martin Škoda [this message]
2026-11-13 17:13   ` Jochen Philipp
2026-11-16  6:59     ` Johannes Thumshirn
2026-11-16  8:56       ` Dongjiang Zhu
2026-11-16 15:08   ` Mark Korenberg

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=e3261fe5-4b98-47e6-ae66-d4af05caa621@gmail.com \
    --to=mar.skoda@gmail.com \
    --cc=a2jphilipp@gmail.com \
    --cc=dsterba@suse.com \
    --cc=johannes.thumshirn@wdc.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=naohiro.aota@wdc.com \
    --cc=zhudongjiang@fygo.io \
    /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