canonical-ubuntu-qa team mailing list archive

[LEE KUAN-YING <2103682@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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)

** Affects: ubuntu-kernel-tests
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2103682

Title:
  ubuntu_btrfs_kernel_fixes failed on N-oem-6.11

Status in ubuntu-kernel-tests:
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2103682/+subscriptions