# BTRFS errors possibly patched by LTSS kernel patch **URL:** \ **Category:** SLES Updates\ **Created:** [April 26, 2017, 8:27am UTC](https://forums.suse.com/t/btrfs-errors-possibly-patched-by-ltss-kernel-patch/29714 "2017-04-26T08:27:16Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![svensimon](https://avatars.discourse-cdn.com/v4/letter/s/e19b73/32.png) [@svensimon](https://forums.suse.com/u/svensimon)\ **Post date:** [April 26, 2017, 8:27am UTC](https://forums.suse.com/t/btrfs-errors-possibly-patched-by-ltss-kernel-patch/29714/1 "2017-04-26T08:27:16Z")
On our SLES12 machines with 3.12.60-52.54-default, the last one available with general support, I’m seeing a lot of the following errors: [1162618.189883] ------------[cut here]------------ [1162618.189912] WARNING: CPU: 2 PID: 39991 at …/fs/btrfs/extent-tree.c:3731 btrfs\_free\_reserved\_data\_space\_noquota+0xe8/0x100 btrfs [1162618.189914] Modules linked in: binfmt\_misc ipmi\_si nfsv3 nfs\_acl rpcsec\_gss\_krb5 auth\_rpcgss nfsv4 dns\_resolver nfs lockd sunrpc fscache mpt3sas mpt2sas raid\_class scsi\_transpor t\_sas mptctl mptbase af\_packet dell\_rbu(X) iscsi\_ibft iscsi\_boot\_sysfs msr joydev hid\_generic usbhid onload(OEN) sfc\_char(OEN) sfc\_resource(OEN) sfc\_affinity(OEN) onload\_cplane(POEN) coretemp kvm\_intel kvm crct10dif\_pclmul crc32\_pclmul sfc(OEN) iTCO\_wdt iTCO\_vendor\_support ipmi\_devintf dcdbas(X) mtd ptp pps\_core mdio aesni\_intel ipmi\_msghandler wmi acpi\_power\_mete r aes\_x86\_64 lpc\_ich mfd\_core lrw gf128mul glue\_helper ablk\_helper shpchp cryptd pcspkr button acpi\_pad processor dm\_mod btrfs xor raid6\_pq sr\_mod cdrom sd\_mod crc32c\_intel mgag200 sy scopyarea sysfillrect sysimgblt i2c\_algo\_bit drm\_kms\_helper ttm drm ahci libahci ehci\_pci ehci\_hcd libata usbcore megaraid\_sas usb\_common sg scsi\_mod autofs4 [last unloaded: ipmi\_si] [1162618.189951] Supported: No, Proprietary and Unsupported modules are loaded [1162618.189954] CPU: 2 PID: 39991 Comm: kworker/u97:2 Tainted: P W OE NX 3.12.60-52.54-default #1 [1162618.189955] Hardware name: Dell Inc. PowerEdge R620/0GFKVD, BIOS 2.4.3 07/09/2014 [1162618.189960] Workqueue: writeback bdi\_writeback\_workfn (flush-btrfs-1) [1162618.189962] 0000000000000000 ffffffff81515330 0000000000000000 ffffffffa02d88af [1162618.189964] ffffffff810554d2 ffff880803ace000 ffff88080440de00 0000000000001000 [1162618.189967] 0000000000001000 ffff8807b481b444 ffffffffa0243318 ffff8807b481b5d0 [1162618.189969] Call Trace: [1162618.189979] [] dump\_trace+0x7d/0x2d0 [1162618.189982] [] show\_stack\_log\_lvl+0x94/0x170 [1162618.189985] [] show\_stack+0x21/0x50 [1162618.189990] [] dump\_stack+0x5d/0x78 [1162618.189995] [] warn\_slowpath\_common+0x82/0xc0 [1162618.190006] [] btrfs\_free\_reserved\_data\_space\_noquota+0xe8/0x100 [btrfs] [1162618.190038] [] btrfs\_clear\_bit\_hook+0x22f/0x2f0 [btrfs] [1162618.190085] [] clear\_state\_bit+0x5c/0x1e0 [btrfs] [1162618.190143] [] \_\_clear\_extent\_bit+0x2b6/0x400 [btrfs] [1162618.190201] [] extent\_clear\_unlock\_delalloc+0x5f/0x250 [btrfs] [1162618.190260] [] cow\_file\_range+0x29c/0x480 [btrfs] [1162618.190304] [] run\_delalloc\_range+0x35a/0x390 [btrfs] [1162618.190350] [] writepage\_delalloc.isra.39+0xfe/0x160 [btrfs] [1162618.190408] [] \_\_extent\_writepage+0xc1/0x2e0 [btrfs] [1162618.190466] [] extent\_write\_cache\_pages.isra.33.constprop.55+0x2af/0x360 [btrfs] [1162618.190526] [] extent\_writepages+0x4d/0x60 [btrfs] [1162618.190577] [] \_\_writeback\_single\_inode+0x39/0x2b0 [1162618.190581] [] writeback\_sb\_inodes+0x1a4/0x400 [1162618.190585] [] \_\_writeback\_inodes\_wb+0x96/0xc0 [1162618.190588] [] wb\_writeback+0x283/0x330 [1162618.190592] [] bdi\_writeback\_workfn+0x1dc/0x480 [1162618.190596] [] process\_one\_work+0x174/0x460 [1162618.190600] [] worker\_thread+0x11a/0x3c0 [1162618.190603] [] kthread+0xb4/0xc0 [1162618.190607] [] ret\_from\_fork+0x58/0x90 [1162618.190610] —[end trace 35b94503d0123787]— I see kernel-default-3.12.61-52.66.1.x86\_64.rpm is available for SLES12 LTSS and has a lot of BTRFS bugfixes. What options do I have for gaining access and being able to download to test that? ---
**Author:** ![smflood](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/smflood/32/10576_2.png) [@smflood](https://forums.suse.com/u/smflood)\ **Post date:** [April 26, 2017, 12:53pm UTC](https://forums.suse.com/t/btrfs-errors-possibly-patched-by-ltss-kernel-patch/29714/2 "2017-04-26T12:53:15Z")
On 26/04/17 06:34, svensimon wrote: [color=blue] > On our SLES12 machines with 3.12.60-52.54-default, the last one > available with general support, I’m seeing a lot of the following > errors: > > [1162618.189883] ------------[cut here]------------ > [1162618.189912] WARNING: CPU: 2 PID: 39991 at > ../fs/btrfs/extent-tree.c:3731 > btrfs\_free\_reserved\_data\_space\_noquota+0xe8/0x100 btrfs > [1162618.189914] Modules linked in: binfmt\_misc ipmi\_si nfsv3 nfs\_acl > rpcsec\_gss\_krb5 auth\_rpcgss nfsv4 dns\_resolver nfs lockd sunrpc fscache > mpt3sas mpt2sas raid\_class scsi\_transpor > t\_sas mptctl mptbase af\_packet dell\_rbu(X) iscsi\_ibft iscsi\_boot\_sysfs > msr joydev hid\_generic usbhid onload(OEN) sfc\_char(OEN) > sfc\_resource(OEN) sfc\_affinity(OEN) onload\_cplane(POEN) > coretemp kvm\_intel kvm crct10dif\_pclmul crc32\_pclmul sfc(OEN) iTCO\_wdt > iTCO\_vendor\_support ipmi\_devintf dcdbas(X) mtd ptp pps\_core mdio > aesni\_intel ipmi\_msghandler wmi acpi\_power\_mete > r aes\_x86\_64 lpc\_ich mfd\_core lrw gf128mul glue\_helper ablk\_helper > shpchp cryptd pcspkr button acpi\_pad processor dm\_mod btrfs xor raid6\_pq > sr\_mod cdrom sd\_mod crc32c\_intel mgag200 sy > scopyarea sysfillrect sysimgblt i2c\_algo\_bit drm\_kms\_helper ttm drm ahci > libahci ehci\_pci ehci\_hcd libata usbcore megaraid\_sas usb\_common sg > scsi\_mod autofs4 [last unloaded: ipmi\_si] > [1162618.189951] Supported: No, Proprietary and Unsupported modules are > loaded > [1162618.189954] CPU: 2 PID: 39991 Comm: kworker/u97:2 Tainted: P > W OE NX 3.12.60-52.54-default #1 > [1162618.189955] Hardware name: Dell Inc. PowerEdge R620/0GFKVD, BIOS > 2.4.3 07/09/2014 > [1162618.189960] Workqueue: writeback bdi\_writeback\_workfn > (flush-btrfs-1) > [1162618.189962] 0000000000000000 ffffffff81515330 0000000000000000 > ffffffffa02d88af > [1162618.189964] ffffffff810554d2 ffff880803ace000 ffff88080440de00 > 0000000000001000 > [1162618.189967] 0000000000001000 ffff8807b481b444 ffffffffa0243318 > ffff8807b481b5d0 > [1162618.189969] Call Trace: > [1162618.189979] [] dump\_trace+0x7d/0x2d0 > [1162618.189982] [] show\_stack\_log\_lvl+0x94/0x170 > [1162618.189985] [] show\_stack+0x21/0x50 > [1162618.189990] [] dump\_stack+0x5d/0x78 > [1162618.189995] [] warn\_slowpath\_common+0x82/0xc0 > [1162618.190006] [] > btrfs\_free\_reserved\_data\_space\_noquota+0xe8/0x100 [btrfs] > [1162618.190038] [] btrfs\_clear\_bit\_hook+0x22f/0x2f0 > [btrfs] > [1162618.190085] [] clear\_state\_bit+0x5c/0x1e0 > [btrfs] > [1162618.190143] [] \_\_clear\_extent\_bit+0x2b6/0x400 > [btrfs] > [1162618.190201] [] > extent\_clear\_unlock\_delalloc+0x5f/0x250 [btrfs] > [1162618.190260] [] cow\_file\_range+0x29c/0x480 > [btrfs] > [1162618.190304] [] run\_delalloc\_range+0x35a/0x390 > [btrfs] > [1162618.190350] [] > writepage\_delalloc.isra.39+0xfe/0x160 [btrfs] > [1162618.190408] [] \_\_extent\_writepage+0xc1/0x2e0 > [btrfs] > [1162618.190466] [] > extent\_write\_cache\_pages.isra.33.constprop.55+0x2af/0x360 [btrfs] > [1162618.190526] [] extent\_writepages+0x4d/0x60 > [btrfs] > [1162618.190577] [] > \_\_writeback\_single\_inode+0x39/0x2b0 > [1162618.190581] [] writeback\_sb\_inodes+0x1a4/0x400 > [1162618.190585] [] \_\_writeback\_inodes\_wb+0x96/0xc0 > [1162618.190588] [] wb\_writeback+0x283/0x330 > [1162618.190592] [] > bdi\_writeback\_workfn+0x1dc/0x480 > [1162618.190596] [] process\_one\_work+0x174/0x460 > [1162618.190600] [] worker\_thread+0x11a/0x3c0 > [1162618.190603] [] kthread+0xb4/0xc0 > [1162618.190607] [] ret\_from\_fork+0x58/0x90 > [1162618.190610] —[end trace 35b94503d0123787]— > > I see kernel-default-3.12.61-52.66.1.x86\_64.rpm is available for SLES12 > LTSS and has a lot of BTRFS bugfixes. What options do I have for gaining > access and being able to download to test that?[/color] You can only get access to SLES12 LTSS patches if you have Long Term Service Pack Support for SLES12 so your options, if you don’t have LTSS for SLES12, are to buy LTSS or upgrade SLES12 (which is now out of General Support, hence LTSS being available) to SLES12 SP1 or (preferrably) SLES12 SP2. ## HTH. Simon SUSE Knowledge Partner * * * ## If you find this post helpful and are logged into the web interface, please show your appreciation and click on the star below. Thanks. ---
**Author:** ![svensimon](https://avatars.discourse-cdn.com/v4/letter/s/e19b73/32.png) [@svensimon](https://forums.suse.com/u/svensimon)\ **Post date:** [April 27, 2017, 8:28am UTC](https://forums.suse.com/t/btrfs-errors-possibly-patched-by-ltss-kernel-patch/29714/3 "2017-04-27T08:28:16Z")
Thanks Simon, unfortunately I don’t have the budget to buy LTSS and the migration away from SLES12 takes longer than anticipated. I’m just looking for a stop-gap solution to make those errors go away which were introduced with the latest kernel from General Support.