btrfs_direct_write hung during copy using dd
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-signed-aws-5.19 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Hi,
I have btrfs filesystem with 2 subvolumes in it. I have copied 48G data to first subvolume and then attached 99G disk to it. Then I started copy 48G to second volume using below dd command[1]. After 3G data copied to second volume dd got stuck with below stack trace[2].
1. dd if=./test1 of=/lucidity_
2. mount point informationubun
ubuntu@
/dev/nvme10n1 on /lucidity_diskpool type btrfs (rw,noatime,
/dev/nvme10n1 on /home/test_mnt type btrfs (rw,noatime,
/dev/nvme10n1 on /lucidity_tmp1 type btrfs (rw,noatime,
3. Stack trace[ 573.977394] Spurious interrupt (vector 0xef) on CPU#0. Acked
[ 573.978949] nvme nvme13: 2/0/0 default/read/poll queues
[ 595.087826] BTRFS info (device nvme10n1): disk added /dev/nvme13n1
[ 968.457121] INFO: task dd:10718 blocked for more than 120 seconds.
[ 968.459372] Not tainted 5.19.0-1025-aws #26~22.04.1-Ubuntu
[ 968.461557] "echo 0 > /proc/sys/
[ 968.464327] task:dd state:D stack: 0 pid:10718 ppid: 10717 flags:0x00004002
[ 968.464332] Call Trace:
[ 968.464334] <TASK>
[ 968.464337] __schedule+
[ 968.464343] schedule+0x5d/0x100
[ 968.464346] io_schedule+
[ 968.464348] blk_mq_
[ 968.464353] ? destroy_
[ 968.464359] __blk_mq_
[ 968.464362] blk_mq_
[ 968.464366] blk_mq_
[ 968.464368] __submit_
[ 968.464370] submit_
[ 968.464372] submit_
[ 968.464374] submit_
[ 968.464378] btrfs_map_
[ 968.464432] ? __bio_clone+
[ 968.464436] btrfs_submit_
[ 968.464467] ? iov_iter_
[ 968.464470] iomap_dio_
[ 968.464473] iomap_dio_
[ 968.464475] __iomap_
[ 968.464479] btrfs_dio_
[ 968.464511] btrfs_direct_
[ 968.464545] btrfs_do_
[ 968.464576] ? rseq_ip_
[ 968.464580] btrfs_file_
[ 968.464612] new_sync_
[ 968.464615] vfs_write+
[ 968.464617] ksys_write+
[ 968.464619] __x64_sys_
[ 968.464621] do_syscall_
[ 968.464624] ? do_syscall_
[ 968.464625] entry_SYSCALL_
[ 968.464629] RIP: 0033:0x7fbeb5f14a37
[ 968.464631] RSP: 002b:00007ffedc
[ 968.464633] RAX: ffffffffffffffda RBX: 0000000002000000 RCX: 00007fbeb5f14a37
[ 968.464635] RDX: 0000000002000000 RSI: 00007fbeb39fe000 RDI: 0000000000000001
[ 968.464636] RBP: 00007fbeb39fe000 R08: 0000000000000400 R09: 00007fbeb39fe000
[ 968.464637] R10: 0000000000000022 R11: 0000000000000246 R12: 0000000000000000
[ 968.464639] R13: 0000000000000400 R14: ffffffffffffffff R15: 00007fbeb39fe000
[ 968.464641] </TASK>
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu
ubuntu@
Description: Ubuntu 22.04.2 LTS
Release: 22.04
2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software
Center
N: Unable to locate package pkgname
3) What you expected to happen
dd command should copy data to subvolume
4) What happened instead
It hung
Thank You
Sushma
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-
ProcVersionSign
Uname: Linux 5.19.0-1025-aws x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckR
Date: Fri Jul 14 10:35:02 2023
Ec2AMI: ami-0395e642c96
Ec2AMIManifest: (unknown)
Ec2Availability
Ec2InstanceType: t3.medium
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=C.UTF-8
SHELL=/bin/bash
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: linux-signed-
UpgradeStatus: No upgrade log present (probably fresh install)