PDA

View Full Version : SLES 12 BTRFS errors possibly patched by LTSS kernel patch



svensimon
26-Apr-2017, 06:27
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] [<ffffffff8100475d>] dump_trace+0x7d/0x2d0
[1162618.189982] [<ffffffff81004a44>] show_stack_log_lvl+0x94/0x170
[1162618.189985] [<ffffffff81005cf1>] show_stack+0x21/0x50
[1162618.189990] [<ffffffff81515330>] dump_stack+0x5d/0x78
[1162618.189995] [<ffffffff810554d2>] warn_slowpath_common+0x82/0xc0
[1162618.190006] [<ffffffffa0243318>] btrfs_free_reserved_data_space_noquota+0xe8/0x100 [btrfs]
[1162618.190038] [<ffffffffa025edcf>] btrfs_clear_bit_hook+0x22f/0x2f0 [btrfs]
[1162618.190085] [<ffffffffa02771fc>] clear_state_bit+0x5c/0x1e0 [btrfs]
[1162618.190143] [<ffffffffa0277bf6>] __clear_extent_bit+0x2b6/0x400 [btrfs]
[1162618.190201] [<ffffffffa0278c1f>] extent_clear_unlock_delalloc+0x5f/0x250 [btrfs]
[1162618.190260] [<ffffffffa026179c>] cow_file_range+0x29c/0x480 [btrfs]
[1162618.190304] [<ffffffffa026286a>] run_delalloc_range+0x35a/0x390 [btrfs]
[1162618.190350] [<ffffffffa02794de>] writepage_delalloc.isra.39+0xfe/0x160 [btrfs]
[1162618.190408] [<ffffffffa027a1a1>] __extent_writepage+0xc1/0x2e0 [btrfs]
[1162618.190466] [<ffffffffa027a66f>] extent_write_cache_pages.isra.33.constprop.55+0x2a f/0x360 [btrfs]
[1162618.190526] [<ffffffffa027c57d>] extent_writepages+0x4d/0x60 [btrfs]
[1162618.190577] [<ffffffff811cab69>] __writeback_single_inode+0x39/0x2b0
[1162618.190581] [<ffffffff811cb8c4>] writeback_sb_inodes+0x1a4/0x400
[1162618.190585] [<ffffffff811cbbb6>] __writeback_inodes_wb+0x96/0xc0
[1162618.190588] [<ffffffff811cbe63>] wb_writeback+0x283/0x330
[1162618.190592] [<ffffffff811cd66c>] bdi_writeback_workfn+0x1dc/0x480
[1162618.190596] [<ffffffff81070264>] process_one_work+0x174/0x460
[1162618.190600] [<ffffffff81070f1a>] worker_thread+0x11a/0x3c0
[1162618.190603] [<ffffffff81077884>] kthread+0xb4/0xc0
[1162618.190607] [<ffffffff81523598>] 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?

smflood
26-Apr-2017, 10:53
On 26/04/17 06:34, svensimon wrote:

> 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] [<ffffffff8100475d>] dump_trace+0x7d/0x2d0
> [1162618.189982] [<ffffffff81004a44>] show_stack_log_lvl+0x94/0x170
> [1162618.189985] [<ffffffff81005cf1>] show_stack+0x21/0x50
> [1162618.189990] [<ffffffff81515330>] dump_stack+0x5d/0x78
> [1162618.189995] [<ffffffff810554d2>] warn_slowpath_common+0x82/0xc0
> [1162618.190006] [<ffffffffa0243318>]
> btrfs_free_reserved_data_space_noquota+0xe8/0x100 [btrfs]
> [1162618.190038] [<ffffffffa025edcf>] btrfs_clear_bit_hook+0x22f/0x2f0
> [btrfs]
> [1162618.190085] [<ffffffffa02771fc>] clear_state_bit+0x5c/0x1e0
> [btrfs]
> [1162618.190143] [<ffffffffa0277bf6>] __clear_extent_bit+0x2b6/0x400
> [btrfs]
> [1162618.190201] [<ffffffffa0278c1f>]
> extent_clear_unlock_delalloc+0x5f/0x250 [btrfs]
> [1162618.190260] [<ffffffffa026179c>] cow_file_range+0x29c/0x480
> [btrfs]
> [1162618.190304] [<ffffffffa026286a>] run_delalloc_range+0x35a/0x390
> [btrfs]
> [1162618.190350] [<ffffffffa02794de>]
> writepage_delalloc.isra.39+0xfe/0x160 [btrfs]
> [1162618.190408] [<ffffffffa027a1a1>] __extent_writepage+0xc1/0x2e0
> [btrfs]
> [1162618.190466] [<ffffffffa027a66f>]
> extent_write_cache_pages.isra.33.constprop.55+0x2a f/0x360 [btrfs]
> [1162618.190526] [<ffffffffa027c57d>] extent_writepages+0x4d/0x60
> [btrfs]
> [1162618.190577] [<ffffffff811cab69>]
> __writeback_single_inode+0x39/0x2b0
> [1162618.190581] [<ffffffff811cb8c4>] writeback_sb_inodes+0x1a4/0x400
> [1162618.190585] [<ffffffff811cbbb6>] __writeback_inodes_wb+0x96/0xc0
> [1162618.190588] [<ffffffff811cbe63>] wb_writeback+0x283/0x330
> [1162618.190592] [<ffffffff811cd66c>]
> bdi_writeback_workfn+0x1dc/0x480
> [1162618.190596] [<ffffffff81070264>] process_one_work+0x174/0x460
> [1162618.190600] [<ffffffff81070f1a>] worker_thread+0x11a/0x3c0
> [1162618.190603] [<ffffffff81077884>] kthread+0xb4/0xc0
> [1162618.190607] [<ffffffff81523598>] 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?

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.
------------------------------------------------------------------------

svensimon
27-Apr-2017, 06:28
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.