From: Christoph Hellwig <hch@lst.de>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Naohiro Aota <Naohiro.Aota@wdc.com>,
Johannes Thumshirn <Johannes.Thumshirn@wdc.com>,
linux-btrfs@vger.kernel.org
Subject: new scrub code vs zoned file systems
Date: Wed, 31 May 2023 14:52:24 +0200 [thread overview]
Message-ID: <20230531125224.GB27468@lst.de> (raw)
Hi Qu,
btrfs/163 got really unhappy on zoned devices with the new scrub code,
as it tries to rewrite data in place using btrfs_submit_repair_write,
which is a regression compared to say Linux 6.3.
This log is when running on a SCRATCH_POOL using qemu emulated ZNS
drives:
[ 53.359190] BTRFS info (device nvme1n1): host-managed zoned block device /dev/nvme3n1, 160 zones of 134217728 bytes
[ 53.360646] BTRFS info (device nvme1n1): dev_replace from /dev/nvme2n1 (devid 2) to /dev/nvme3n1 started
[ 53.691003] nvme3n1: Zone Management Append(0x7d) @ LBA 65536, 4 blocks, Zone Is Full (sct 0x1 / sc 0xb9) DNR
[ 53.694996] I/O error, dev nvme3n1, sector 786432 op 0xd:(ZONE_APPEND) flags 0x4000 phys_seg 3 prio class 2
[ 53.694996] BTRFS error (device nvme1n1): bdev /dev/nvme3n1 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0
[ 53.694996] BUG: kernel NULL pointer dereference, address: 00000000000000a8
[ 53.694996] #PF: supervisor write access in kernel mode
[ 53.694996] #PF: error_code(0x0002) - not-present page
[ 53.694996] PGD 0 P4D 0
[ 53.694996] Oops: 0002 [#1] PREEMPT SMP NOPTI
[ 53.694996] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 6.4.0-rc2+ #1190
[ 53.694996] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014
[ 53.694996] RIP: 0010:_raw_spin_lock_irqsave+0x1e/0x40
[ 53.694996] Code: c2 fe c3 66 0f 1f 84 00 00 00 00 00 53 9c 58 0f 1f 40 00 48 89 c3 fa 0f 1f 44 00 00 65 ff 05 21 e7 c4 7d 31 c0 ba 01 00 00 00 <f0> 0f b1 17 75 05 48 89 d8 5b c3 89 c6 e8 10 03 00 00 48 89 d8 5b
[ 53.694996] RSP: 0018:ffffc900000c4e00 EFLAGS: 00010046
[ 53.694996] RAX: 0000000000000000 RBX: 0000000000000046 RCX: 0000000000000027
[ 53.694996] RDX: 0000000000000001 RSI: 0000000000000000 RDI: 00000000000000a8
[ 53.694996] RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000003
[ 53.694996] R10: ffffffff83076000 R11: ffffffff83076000 R12: ffff88810adecc00
[ 53.694996] R13: 00000000000000a8 R14: 0000000000004000 R15: 0000000000004000
[ 53.694996] FS: 0000000000000000(0000) GS:ffff888277d00000(0000) knlGS:0000000000000000
[ 53.694996] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 53.694996] CR2: 00000000000000a8 CR3: 0000000103544000 CR4: 0000000000750ee0
[ 53.694996] PKRU: 55555554
[ 53.694996] Call Trace:
[ 53.694996] <IRQ>
[ 53.694996] btrfs_lookup_ordered_extent+0x31/0x190
[ 53.694996] btrfs_record_physical_zoned+0x18/0x40
[ 53.694996] btrfs_simple_end_io+0xaf/0xc0
[ 53.694996] blk_update_request+0x153/0x4c0
[ 53.694996] blk_mq_end_request+0x15/0xd0
[ 53.694996] nvme_poll_cq+0x1d3/0x360
[ 53.694996] nvme_irq+0x39/0x80
[ 53.694996] __handle_irq_event_percpu+0x3b/0x190
[ 53.694996] handle_irq_event+0x2f/0x70
[ 53.694996] handle_edge_irq+0x7c/0x210
[ 53.694996] __common_interrupt+0x34/0xa0
[ 53.694996] common_interrupt+0x7d/0xa0
[ 53.694996] </IRQ>
[ 53.694996] <TASK>
[ 53.694996] asm_common_interrupt+0x22/0x40
next reply other threads:[~2023-05-31 12:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 12:52 Christoph Hellwig [this message]
2023-05-31 13:10 ` new scrub code vs zoned file systems Johannes Thumshirn
2023-05-31 13:20 ` Christoph Hellwig
2023-05-31 13:25 ` Johannes Thumshirn
2023-05-31 13:30 ` Christoph Hellwig
2023-05-31 14:04 ` Johannes Thumshirn
2023-05-31 14:17 ` Christoph Hellwig
2023-06-01 2:09 ` Qu Wenruo
2023-06-01 4:40 ` Christoph Hellwig
2023-06-01 5:00 ` Qu Wenruo
2023-06-01 5:17 ` Naohiro Aota
2023-06-01 5:21 ` Naohiro Aota
2023-06-01 7:21 ` Qu Wenruo
2023-06-01 7:27 ` Christoph Hellwig
2023-06-01 8:46 ` Qu Wenruo
2023-06-01 5:22 ` Christoph Hellwig
2023-06-01 5:34 ` Christoph Hellwig
2023-06-01 5:45 ` Qu Wenruo
2023-06-01 5:47 ` Christoph Hellwig
2023-05-31 22:25 ` Qu Wenruo
2023-05-31 22:48 ` Qu Wenruo
2023-06-01 4:53 ` Christoph Hellwig
2023-06-01 5:04 ` Qu Wenruo
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=20230531125224.GB27468@lst.de \
--to=hch@lst.de \
--cc=Johannes.Thumshirn@wdc.com \
--cc=Naohiro.Aota@wdc.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.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