f88ba6a2a in ubuntu_btrfs_kernel_fixes failed on J-OEM-5.17

Bug #1973261 reported by Po-Hsu Lin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
New
Undecided
Unassigned
linux-oem-5.17 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Issue found on Jammy OEM 5.17.0-1004.4

Test output:
  Invoking test f88ba6a2a44ee98e8d59654463dc157bb6d13c43

  fix f88ba6a2a44ee98e8d59654463dc157bb6d13c43

      Btrfs: skip submitting barrier for missing device

      I got an error on v3.13:
       BTRFS error (device sdf1) in write_all_supers:3378: errno=-5 IO failure (errors while submitting device barriers.)

      how to reproduce:
        > mkfs.btrfs -f -d raid1 /dev/sdf1 /dev/sdf2
        > wipefs -a /dev/sdf2
        > mount -o degraded /dev/sdf1 /mnt
        > btrfs balance start -f -sconvert=single -mconvert=single -dconvert=single /mnt

      The reason of the error is that barrier_all_devices() failed to submit
      barrier to the missing device. However it is clear that we cannot do
      anything on missing device, and also it is not necessary to care chunks
      on the missing device.

      This patch stops sending/waiting barrier if device is missing.

  btrfs balance failed on /tmp/mnt-f88ba6a2a44ee98e8d59654463dc157bb6d13c43

  FAIL: f88ba6a2a44ee98e8d59654463dc157bb6d13c43 (ret=1)

dmesg output:

[ 390.757211] Invoking test f88ba6a2a44ee98e8d59654463dc157bb6d13c43
[ 390.773367] loop6: detected capacity change from 0 to 2097152
[ 390.801666] loop7: detected capacity change from 0 to 2097152
[ 392.126867] BTRFS: device fsid 3c464492-2cf2-4feb-a6fd-26f90d644196 devid 1 transid 6 /dev/loop6 scanned by systemd-udevd (1407)
[ 392.196398] BTRFS: device fsid 3c464492-2cf2-4feb-a6fd-26f90d644196 devid 2 transid 6 /dev/loop7 scanned by mkfs.btrfs (1409)
[ 392.548599] BTRFS info (device loop6): flagging fs with big metadata feature
[ 392.548610] BTRFS info (device loop6): allowing degraded mounts
[ 392.548614] BTRFS info (device loop6): using free space tree
[ 392.548617] BTRFS info (device loop6): has skinny extents
[ 392.549304] BTRFS warning (device loop6): devid 2 uuid 918c3e31-5c12-491e-aac0-a007eda45078 is missing
[ 392.549434] BTRFS warning (device loop6): devid 2 uuid 918c3e31-5c12-491e-aac0-a007eda45078 is missing
[ 392.550341] BTRFS info (device loop6): checking UUID tree
[ 392.562271] BTRFS info (device loop6): balance: force reducing metadata redundancy
[ 392.622941] BTRFS info (device loop6): balance: start -f -dconvert=single -mconvert=single -sconvert=single
[ 392.623003] BTRFS info (device loop6): relocating block group 362545152 flags system
[ 392.742941] BTRFS info (device loop6): relocating block group 245104640 flags metadata
[ 393.004397] BTRFS info (device loop6): relocating block group 137756672 flags data|raid1
[ 393.298466] BTRFS info (device loop6): relocating block group 30408704 flags metadata|raid1
[ 393.591373] BTRFS info (device loop6): found 7 extents, stage: move data extents
[ 393.959629] BTRFS info (device loop6): relocating block group 22020096 flags system|raid1
[ 394.210882] BTRFS info (device loop6): 1 enospc errors during balance
[ 394.210893] BTRFS info (device loop6): balance: ended with status: -28
[ 394.437519] Test f88ba6a2a44ee98e8d59654463dc157bb6d13c43 returned 0

This is not a regression as this failure can be found with 5.17.0-1002.2 / 5.17.0-1003.3 as well.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.17.0-1004-oem 5.17.0-1004.4
ProcVersionSignature: User Name 5.17.0-1004.4-oem 5.17.3
Uname: Linux 5.17.0-1004-oem x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Fri May 13 05:52:35 2022
SourcePackage: linux-signed-oem-5.17
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
tags: added: 5.17 oem ubuntu-btrfs-kernel-fixes
Po-Hsu Lin (cypressyew)
affects: linux-signed-oem-5.17 (Ubuntu) → linux-oem-5.17 (Ubuntu)
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

This issue can be reproduced with 5.18.0-051800rc6-generic as well.

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

This issue does not exist on J-oem-6.0.0-1002.2

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

we'll migrate oem-5.17 to -6.0 by december, so maybe fixing this is no longer a priority

Changed in linux-oem-5.17 (Ubuntu):
status: New → Won't Fix
Revision history for this message
Magali Lemes do Sacramento (magalilemes) wrote :

Found on Jammy 5.15.0-70.77+fips1 on openstack, 2023-03-20 cycle.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.