btrfs: do not clear read-only when adding sprout device After I revert the above patch, the issue is gone.
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.11 in Ubuntu. https://bugs.launchpad.net/bugs/2103682 Title: ubuntu_btrfs_kernel_fixes failed on N-oem-6.11 Status in ubuntu-kernel-tests: New Status in linux-oem-6.11 package in Ubuntu: New Status in linux-oem-6.11 source package in Noble: New Bug description: Label: (null) UUID: 95a500a1-e39f-4257-97c0-c0580bdbe736 Node size: 16384 Sector size: 4096 Filesystem size: 2.00GiB Block group profiles: Data: single 8.00MiB Metadata: RAID1 102.38MiB System: RAID1 8.00MiB SSD detected: no Zoned device: no Incompat features: extref, skinny-metadata, no-holes, free-space-tree Runtime features: free-space-tree Checksum: crc32c Number of devices: 2 Devices: ID SIZE PATH 1 1.00GiB /dev/loop0 2 1.00GiB /dev/loop1 ERROR: error adding device '/dev/loop3': Read-only file system WARNING: Multiple block group profiles detected, see 'man btrfs(5)' WARNING: Metadata: single, raid1 Performing full device TRIM /dev/loop2 (1.00GiB) ... Performing full device TRIM /dev/loop3 (1.00GiB) ... btrfs device add /dev/loop2 /dev/loop3 /tmp/mnt-671415b7db49f62896f0b6d50fc4f312a0512983 failed ... Steps to reproduce: # mkfs.btrfs -m raid1 # btrfstune -S 1 # mount # btrfs device add # mount -o remount,rw # dd if=/dev/zero of=/tmpfile bs=1M count=1 Deadlock happened. btrfs-progs v6.6.3 See https://btrfs.readthedocs.io for more information. Performing full device TRIM /dev/loop0 (1.00GiB) ... Performing full device TRIM /dev/loop1 (1.00GiB) ... NOTE: several default settings have changed in version 5.15, please make sure this does not affect your deployments: - DUP for metadata (-m dup) - enabled no-holes (-O no-holes) - enabled free-space-tree (-R free-space-tree) Label: (null) UUID: 95a500a1-e39f-4257-97c0-c0580bdbe736 Node size: 16384 Sector size: 4096 Filesystem size: 2.00GiB Block group profiles: Data: single 8.00MiB Metadata: RAID1 102.38MiB System: RAID1 8.00MiB SSD detected: no Zoned device: no Incompat features: extref, skinny-metadata, no-holes, free-space-tree Runtime features: free-space-tree Checksum: crc32c Number of devices: 2 Devices: ID SIZE PATH 1 1.00GiB /dev/loop0 2 1.00GiB /dev/loop1 ERROR: error adding device '/dev/loop3': Read-only file system WARNING: Multiple block group profiles detected, see 'man btrfs(5)' WARNING: Metadata: single, raid1 Performing full device TRIM /dev/loop2 (1.00GiB) ... Performing full device TRIM /dev/loop3 (1.00GiB) ... btrfs device add /dev/loop2 /dev/loop3 /tmp/mnt-671415b7db49f62896f0b6d50fc4f312a0512983 failed FAIL: 671415b7db49f62896f0b6d50fc4f312a0512983 (ret=1) dmesg output from a manual test: [ 113.423686] Invoking test 671415b7db49f62896f0b6d50fc4f312a0512983 [ 113.434257] loop0: detected capacity change from 0 to 2097152 [ 113.437345] loop1: detected capacity change from 0 to 2097152 [ 113.440622] loop2: detected capacity change from 0 to 2097152 [ 113.447844] loop3: detected capacity change from 0 to 2097152 [ 113.520515] BTRFS: device fsid 821f9874-df4d-4e70-a10e-35c48662fc21 devid 1 transid 6 /dev/loop0 (7:0) scanned by mkfs.btrfs (1878) [ 113.520627] BTRFS: device fsid 821f9874-df4d-4e70-a10e-35c48662fc21 devid 2 transid 6 /dev/loop1 (7:1) scanned by mkfs.btrfs (1878) [ 113.554798] BTRFS info (device loop0): first mount of filesystem 821f9874-df4d-4e70-a10e-35c48662fc21 [ 113.554827] BTRFS info (device loop0): using crc32c (crc32c-intel) checksum algorithm [ 113.554832] BTRFS info (device loop0): using free-space-tree [ 113.591732] BTRFS info (device loop0): relocating block group 255197184 flags system [ 113.597470] BTRFS info (device loop0): found 1 extents, stage: move data extents [ 113.601712] BTRFS info (device loop0): relocating block group 22020096 flags system|raid1 [ 113.607623] BTRFS info (device loop0): disk added /dev/loop2 [ 113.621211] Test 671415b7db49f62896f0b6d50fc4f312a0512983 returned 0 [ 123.646494] BTRFS info (device loop0): last unmount of filesystem 9666e6e9-6894-4493-bb04-79293b02fc15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2103682/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp