[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#916619: marked as done ([linux] WARN_ON() in btrfs_put_block_group and btrfs_free_block_groups hit on unmount of btrfs)

Your message dated Thu, 02 Jan 2020 09:27:55 +0100
with message-id <07e70425387e463d9cace23a5b4a420aba89d238.camel@debian.org>
and subject line 
has caused the Debian Bug report #916619,
regarding [linux] WARN_ON() in btrfs_put_block_group and btrfs_free_block_groups hit on unmount of btrfs
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
916619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916619
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux
Version: 4.18.20-2
Severity: normal

--- Please enter the report below this line. ---
Hi,

I use sbuild + schroot + Btrfs snapshots to build packages. I can
reproduce the following two warnings in the journal, after I built at
least one package and unmount the Btrfs filesystem including all its
subvolumes:

Dez 16 06:44:48 flutschi kernel: WARNING: CPU: 7 PID: 15657 at /build/linux-F3l5KA/linux-4.18.20/fs/btrfs/extent-tree.c:110 btrfs_put_block_group+0x4b/0x50 [btrfs]
Dez 16 06:44:48 flutschi kernel: Modules linked in: dm_snapshot dm_bufio fuse rfcomm cmac bnep cpufreq_userspace cpufreq_powersave cpufreq_conservative binfmt_misc nls_ascii nls_cp437 vfat fat btusb btrtl intel_rapl btbcm x86_pkg_temp_thermal intel_powerclamp btintel blue
Dez 16 06:44:48 flutschi kernel:  snd acpi_pad pcc_cpufreq soundcore evdev sunrpc parport_pc ppdev lp parport efivarfs ip_tables x_tables autofs4 btrfs xor zstd_decompress zstd_compress xxhash raid6_pq libcrc32c crc32c_generic algif_skcipher af_alg hid_generic usbhid hid 
Dez 16 06:44:48 flutschi kernel: CPU: 7 PID: 15657 Comm: umount Tainted: G        W         4.18.0-3-amd64 #1 Debian 4.18.20-2
Dez 16 06:44:48 flutschi kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H97M Pro4, BIOS P2.30 03/07/2018
Dez 16 06:44:48 flutschi kernel: RIP: 0010:btrfs_put_block_group+0x4b/0x50 [btrfs]
Dez 16 06:44:48 flutschi kernel: Code: 01 00 00 48 85 c0 75 1a 48 89 fb 48 8b bf d8 00 00 00 e8 d8 fc 8a dd 48 89 df 5b e9 cf fc 8a dd 5b c3 0f 0b eb e2 0f 0b eb cb <0f> 0b eb ce 90 0f 1f 44 00 00 41 55 41 54 49 89 fc 55 53 48 8d 9f 
Dez 16 06:44:48 flutschi kernel: RSP: 0018:ffffb138c1a47de0 EFLAGS: 00010206
Dez 16 06:44:48 flutschi kernel: RAX: 0000000000000000 RBX: ffff9f95d9266090 RCX: e38e38e38e38e38f
Dez 16 06:44:48 flutschi kernel: RDX: 0000000080000000 RSI: 0000000000007000 RDI: ffff9f971b14dc00
Dez 16 06:44:48 flutschi kernel: RBP: ffff9f95d9266000 R08: 0000000000000000 R09: ffffffffc09e6700
Dez 16 06:44:48 flutschi kernel: R10: ffff9f95e9c25438 R11: 0000000000000001 R12: ffff9f971b14dc00
Dez 16 06:44:48 flutschi kernel: R13: ffff9f95d92660a0 R14: ffff9f971b14dce0 R15: dead000000000100
Dez 16 06:44:48 flutschi kernel: FS:  00007f3d7c6e1080(0000) GS:ffff9f972ebc0000(0000) knlGS:0000000000000000
Dez 16 06:44:48 flutschi kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Dez 16 06:44:48 flutschi kernel: CR2: 00005585912ca4b8 CR3: 000000041350a001 CR4: 00000000001606e0
Dez 16 06:44:48 flutschi kernel: Call Trace:
Dez 16 06:44:48 flutschi kernel:  btrfs_free_block_groups+0x131/0x3c0 [btrfs]
Dez 16 06:44:48 flutschi kernel:  close_ctree+0x134/0x2f0 [btrfs]
Dez 16 06:44:48 flutschi kernel:  generic_shutdown_super+0x6c/0x120
Dez 16 06:44:48 flutschi kernel:  kill_anon_super+0xe/0x20
Dez 16 06:44:48 flutschi kernel:  btrfs_kill_super+0x13/0x100 [btrfs]
Dez 16 06:44:48 flutschi kernel:  deactivate_locked_super+0x3a/0x70
Dez 16 06:44:48 flutschi kernel:  cleanup_mnt+0x3b/0x70
Dez 16 06:44:48 flutschi kernel:  task_work_run+0x8a/0xb0
Dez 16 06:44:48 flutschi kernel:  exit_to_usermode_loop+0xe6/0xf0
Dez 16 06:44:48 flutschi kernel:  do_syscall_64+0x10d/0x110
Dez 16 06:44:48 flutschi kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Dez 16 06:44:48 flutschi kernel: RIP: 0033:0x7f3d7cb078c7
Dez 16 06:44:48 flutschi kernel: Code: 15 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 99 15 0c 00 f7 d8 64 89 01 48 
Dez 16 06:44:48 flutschi kernel: RSP: 002b:00007ffe12180268 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
Dez 16 06:44:48 flutschi kernel: RAX: 0000000000000000 RBX: 0000563784c3cb50 RCX: 00007f3d7cb078c7
Dez 16 06:44:48 flutschi kernel: RDX: 0000000000000001 RSI: 0000000000000000 RDI: 0000563784c3d3f0
Dez 16 06:44:48 flutschi kernel: RBP: 0000000000000000 R08: 0000563784c3d0b0 R09: 00007f3d7cb88e80
Dez 16 06:44:48 flutschi kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000563784c3d3f0
Dez 16 06:44:48 flutschi kernel: R13: 00007f3d7cc2d1c4 R14: 0000563784c3cc48 R15: 0000563784c3cd60
Dez 16 06:44:48 flutschi kernel: ---[ end trace a9c69e8425a8a867 ]---
Dez 16 06:44:48 flutschi kernel: WARNING: CPU: 7 PID: 15657 at /build/linux-F3l5KA/linux-4.18.20/fs/btrfs/extent-tree.c:9902 btrfs_free_block_groups+0x290/0x3c0 [btrfs]
Dez 16 06:44:48 flutschi kernel: Modules linked in: dm_snapshot dm_bufio fuse rfcomm cmac bnep cpufreq_userspace cpufreq_powersave cpufreq_conservative binfmt_misc nls_ascii nls_cp437 vfat fat btusb btrtl intel_rapl btbcm x86_pkg_temp_thermal intel_powerclamp btintel blue
Dez 16 06:44:48 flutschi kernel:  snd acpi_pad pcc_cpufreq soundcore evdev sunrpc parport_pc ppdev lp parport efivarfs ip_tables x_tables autofs4 btrfs xor zstd_decompress zstd_compress xxhash raid6_pq libcrc32c crc32c_generic algif_skcipher af_alg hid_generic usbhid hid 
Dez 16 06:44:48 flutschi kernel: CPU: 7 PID: 15657 Comm: umount Tainted: G        W         4.18.0-3-amd64 #1 Debian 4.18.20-2
Dez 16 06:44:48 flutschi kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H97M Pro4, BIOS P2.30 03/07/2018
Dez 16 06:44:48 flutschi kernel: RIP: 0010:btrfs_free_block_groups+0x290/0x3c0 [btrfs]
Dez 16 06:44:48 flutschi kernel: Code: 85 38 14 00 00 48 39 c6 0f 84 bc 00 00 00 49 bf 00 01 00 00 00 00 ad de 48 8b 9d 38 14 00 00 48 83 7b 90 00 0f 84 b1 00 00 00 <0f> 0b 48 8d b3 78 ff ff ff 31 c9 31 d2 48 89 ef e8 eb 41 ff ff 48 
Dez 16 06:44:48 flutschi kernel: RSP: 0018:ffffb138c1a47df0 EFLAGS: 00010206
Dez 16 06:44:48 flutschi kernel: RAX: ffff9f971676e888 RBX: ffff9f971676e888 RCX: 00000000820001e6
Dez 16 06:44:48 flutschi kernel: RDX: 00000000820001e7 RSI: 0000000000000001 RDI: ffff9f971e403c80
Dez 16 06:44:48 flutschi kernel: RBP: ffff9f95d9266000 R08: 0000000000000000 R09: ffffffffc0983c00
Dez 16 06:44:48 flutschi kernel: R10: ffff9f971c0eb3f8 R11: 0000000000000001 R12: ffff9f971676cff8
Dez 16 06:44:48 flutschi kernel: R13: ffff9f971676cff8 R14: 0000000000000000 R15: dead000000000100
Dez 16 06:44:48 flutschi kernel: FS:  00007f3d7c6e1080(0000) GS:ffff9f972ebc0000(0000) knlGS:0000000000000000
Dez 16 06:44:48 flutschi kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Dez 16 06:44:48 flutschi kernel: CR2: 00005585912ca4b8 CR3: 000000041350a001 CR4: 00000000001606e0
Dez 16 06:44:48 flutschi kernel: Call Trace:
Dez 16 06:44:48 flutschi kernel:  close_ctree+0x134/0x2f0 [btrfs]
Dez 16 06:44:48 flutschi kernel:  generic_shutdown_super+0x6c/0x120
Dez 16 06:44:48 flutschi kernel:  kill_anon_super+0xe/0x20
Dez 16 06:44:48 flutschi kernel:  btrfs_kill_super+0x13/0x100 [btrfs]
Dez 16 06:44:48 flutschi kernel:  deactivate_locked_super+0x3a/0x70
Dez 16 06:44:48 flutschi kernel:  cleanup_mnt+0x3b/0x70
Dez 16 06:44:48 flutschi kernel:  task_work_run+0x8a/0xb0
Dez 16 06:44:48 flutschi kernel:  exit_to_usermode_loop+0xe6/0xf0
Dez 16 06:44:48 flutschi kernel:  do_syscall_64+0x10d/0x110
Dez 16 06:44:48 flutschi kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Dez 16 06:44:48 flutschi kernel: RIP: 0033:0x7f3d7cb078c7
Dez 16 06:44:48 flutschi kernel: Code: 15 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 99 15 0c 00 f7 d8 64 89 01 48 
Dez 16 06:44:48 flutschi kernel: RSP: 002b:00007ffe12180268 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
Dez 16 06:44:48 flutschi kernel: RAX: 0000000000000000 RBX: 0000563784c3cb50 RCX: 00007f3d7cb078c7
Dez 16 06:44:48 flutschi kernel: RDX: 0000000000000001 RSI: 0000000000000000 RDI: 0000563784c3d3f0
Dez 16 06:44:48 flutschi kernel: RBP: 0000000000000000 R08: 0000563784c3d0b0 R09: 00007f3d7cb88e80
Dez 16 06:44:48 flutschi kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000563784c3d3f0
Dez 16 06:44:48 flutschi kernel: R13: 00007f3d7cc2d1c4 R14: 0000563784c3cc48 R15: 0000563784c3cd60
Dez 16 06:44:48 flutschi kernel: ---[ end trace a9c69e8425a8a868 ]---
Dez 16 06:44:48 flutschi kernel: BTRFS info (device dm-4): space_info 4 has 887390208 free, is not full
Dez 16 06:44:48 flutschi kernel: BTRFS info (device dm-4): space_info total=1073741824, used=186269696, pinned=0, reserved=16384, may_use=0, readonly=65536
Dez 16 06:44:48 flutschi kernel: BTRFS warning (device dm-4): page private not zero on page 919601152
Dez 16 06:44:48 flutschi kernel: BTRFS warning (device dm-4): page private not zero on page 919605248
Dez 16 06:44:48 flutschi kernel: BTRFS warning (device dm-4): page private not zero on page 919609344
Dez 16 06:44:48 flutschi kernel: BTRFS warning (device dm-4): page private not zero on page 919613440


Next time that filesystem, or a subvolume of it, is mounted, these
messages appear in the journal:

Dez 16 07:25:51 flutschi kernel: BTRFS warning (device dm-4): block group 29360128 has wrong amount of free space
Dez 16 07:25:51 flutschi kernel: BTRFS warning (device dm-4): failed to load free space cache for block group 29360128, rebuilding it now

Running btrfsck on the unmounted filesystem confirms there's something
wrong with it. I'm aware that btrfsck is under development, shouldn't
be really trusted, and I did NOT use the --repair option on the
filesystem.


The system configuration:

(0)fuddl@flutschi:~$ sudo btrfs subvolume list /srv/chroots 
[sudo] Passwort für fuddl: 
ID 369 gen 25669 top level 5 path mirror
ID 370 gen 27069 top level 5 path chroots
ID 371 gen 26004 top level 370 path sid
ID 372 gen 24923 top level 370 path stretch

(0)fuddl@flutschi:~$ cat /proc/mounts
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,relatime 0 0
udev /dev devtmpfs rw,nosuid,relatime,size=8032928k,nr_inodes=2008232,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=1610044k,mode=755 0 0
/dev/mapper/vgssd-root / btrfs rw,relatime,ssd,space_cache,subvolid=5,subvol=/ 0 0
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
tmpfs /sys/fs/cgroup tmpfs ro,nosuid,nodev,noexec,mode=755 0 0
cgroup2 /sys/fs/cgroup/unified cgroup2 rw,nosuid,nodev,noexec,relatime,nsdelegate 0 0
cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,name=systemd 0 0
pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0
efivarfs /sys/firmware/efi/efivars efivarfs rw,nosuid,nodev,noexec,relatime 0 0
bpf /sys/fs/bpf bpf rw,nosuid,nodev,noexec,relatime,mode=700 0 0
cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0
cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
cgroup /sys/fs/cgroup/perf_event cgroup rw,nosuid,nodev,noexec,relatime,perf_event 0 0
cgroup /sys/fs/cgroup/pids cgroup rw,nosuid,nodev,noexec,relatime,pids 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
cgroup /sys/fs/cgroup/net_cls,net_prio cgroup rw,nosuid,nodev,noexec,relatime,net_cls,net_prio 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0
systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=34,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=16928 0 0
systemd-1 /mnt/backups autofs rw,relatime,fd=41,pgrp=1,timeout=30,minproto=5,maxproto=5,direct,pipe_ino=16949 0 0
mqueue /dev/mqueue mqueue rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
hugetlbfs /dev/hugepages hugetlbfs rw,relatime,pagesize=2M 0 0
sunrpc /run/rpc_pipefs rpc_pipefs rw,relatime 0 0
/dev/sdb2 /boot btrfs rw,relatime,ssd,space_cache,subvolid=5,subvol=/ 0 0
/dev/sdb1 /boot/efi vfat rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/mapper/vg0-haufen /srv/chroots btrfs rw,relatime,space_cache,subvolid=370,subvol=/chroots 0 0
/dev/mapper/vg0-haufen /srv/mirror btrfs rw,relatime,space_cache,subvolid=369,subvol=/mirror 0 0
/dev/mapper/vg0-home /home btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0
tmpfs /run/user/1000 tmpfs rw,nosuid,nodev,relatime,size=1610040k,mode=700,uid=1000,gid=1000 0 0
gvfsd-fuse /run/user/1000/gvfs fuse.gvfsd-fuse rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 0 0
fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0


I've got two confgurations for schroot, both using the Btrfs subvolumes
sid and stretch:

(0)fuddl@flutschi:~$ cat /etc/schroot/chroot.d/sid 
[sid]
aliases=default,unstable
type=btrfs-snapshot
description=Debian sid Btrfs snapshot
groups=root,sbuild,fuddl
root-groups=root,sbuild,fuddl
root-users=fuddl
source-root-users=fuddl
btrfs-source-subvolume=/srv/chroots/sid
btrfs-snapshot-directory=/srv/chroots/snapshots
(0)fuddl@flutschi:~$ cat /etc/schroot/chroot.d/stretch 
[stretch]
aliases=stable
type=btrfs-snapshot
description=Debian stretch Btrfs snapshot
groups=root,sbuild,fuddl
root-groups=root,sbuild,fuddl
root-users=fuddl
source-root-users=fuddl
btrfs-source-subvolume=/srv/chroots/stretch
btrfs-snapshot-directory=/srv/chroots/snapshots


To reproduce, I apt source --download-only nexuiz && sbuild --
chroot=sid nexuiz*.dsc (there's no reason to chose exactly this
package. I chose it because I know it has a rather short build time).
After it has built successfully, I can either shutdown the system and
find the above warnings at the end of journcalctl -k -b-1, or I
manually do umount /srv/chroots ; umount /srv/mirror (The latter
resides on the same btrfs filesystem and all subvolumes must be
unmounted to trigger the warning) and the warnings appear immediately
in the journal.

I reproduced the issue with those two disk configurations:
   1. External USB disk -> GPT partition -> btrfs
   2. Internal SATA disk -> GPT partition -> dm-crypt -> lvm -> btrfs

Creating snapshots by hand with btrfs subvolume snapshot […], writing,
deleting small, large and/or many files on the snapshot did not result
in the warnings on unmount as with using sbuild. Therefore, I
unfortunately didn't manage to find a smaller example.

Cheers - Bruno

--- System information. ---
Architecture: 
Kernel:       Linux 4.18.0-3-amd64

Debian Release: buster/sid
  500 unstable-debug  deb.debian.org 
  500 unstable        deb.debian.org 
    1 experimental-debug deb.debian.org 
    1 experimental    deb.debian.org 

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
--- Begin Message --- 
Version: 5.4.6-1

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: