* call trace: WARNING: at /build/linux-uwVqDp/linux-4.16.16/fs/btrfs/ctree.h:1565 btrfs_update_device
@ 2018-06-28 13:19 Christoph Anton Mitterer
2018-06-28 13:25 ` Nikolay Borisov
2018-06-28 14:09 ` Qu Wenruo
0 siblings, 2 replies; 9+ messages in thread
From: Christoph Anton Mitterer @ 2018-06-28 13:19 UTC (permalink / raw)
To: linux-btrfs
Hey.
On a 4.16.16 kernel with a RAID 1 btrfs I got the following messages
since today.
Data seems still to be readable (correctly)... and there are no other
errors (like SATA errors) in the kernel log.
Any idea what these could mean?
Thanks,
Chris.
[ 72.168662] WARNING: CPU: 0 PID: 242 at /build/linux-uwVqDp/linux-4.16.16/fs/btrfs/ctree.h:1565 btrfs_update_device+0x1b2/0x1c0 [btrfs]
[ 72.168701] Modules linked in: cpufreq_userspace cpufreq_powersave cpufreq_conservative snd_hda_codec_hdmi ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_policy ipt_REJECT nf_reject_ipv4 xt_comment xt_tcpudp nf_conntrack_ipv4 powernow_k8 nf_defrag_ipv4 edac_mce_amd snd_hda_intel kvm_amd snd_hda_codec ccp rng_core snd_hda_core kvm snd_hwdep irqbypass snd_pcm wmi_bmof radeon snd_timer ttm xt_multiport snd pcspkr soundcore drm_kms_helper k8temp ohci_pci ata_generic pata_atiixp ohci_hcd ehci_pci sg wmi xt_conntrack drm nf_conntrack i2c_algo_bit ehci_hcd usbcore button sp5100_tco usb_common shpchp i2c_piix4 iptable_filter binfmt_misc sunrpc hwmon_vid ip_tables x_tables autofs4 btrfs zstd_decompress zstd_compress xxhash sd_mod raid10 raid456 async_raid6_recov
[ 72.168776] async_memcpy async_pq async_xor async_tx libcrc32c crc32c_generic xor raid6_pq raid1 raid0 multipath linear md_mod evdev ahci libahci serio_raw libata r8169 mii scsi_mod
[ 72.168820] CPU: 0 PID: 242 Comm: btrfs-cleaner Not tainted 4.16.0-2-amd64 #1 Debian 4.16.16-2
[ 72.168852] Hardware name: MICRO-STAR INTERNATIONAL CO.,LTD MS-7551/KA780G (MS-7551), BIOS V16.6 05/12/2010
[ 72.168907] RIP: 0010:btrfs_update_device+0x1b2/0x1c0 [btrfs]
[ 72.168939] RSP: 0018:ffffbd5a810a3d60 EFLAGS: 00010206
[ 72.168973] RAX: 0000000000000fff RBX: ffff938e847f8000 RCX: 000000e8a0db1e00
[ 72.169006] RDX: 0000000000001000 RSI: 0000000000003f5c RDI: ffff938e7a8015e0
[ 72.169040] RBP: ffff938e8fb97a00 R08: ffffbd5a810a3d10 R09: ffffbd5a810a3d18
[ 72.169073] R10: 0000000000000003 R11: 0000000000003000 R12: 0000000000000000
[ 72.169106] R13: 0000000000003f3c R14: ffff938e7a8015e0 R15: ffff938e8f0c6328
[ 72.169140] FS: 0000000000000000(0000) GS:ffff938e9dc00000(0000) knlGS:0000000000000000
[ 72.169177] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 72.169210] CR2: 00007fcff92ce000 CR3: 000000020575e000 CR4: 00000000000006f0
[ 72.169243] Call Trace:
[ 72.169304] btrfs_remove_chunk+0x2a9/0x8c0 [btrfs]
[ 72.169359] btrfs_delete_unused_bgs+0x323/0x3f0 [btrfs]
[ 72.169415] ? __btree_submit_bio_start+0x20/0x20 [btrfs]
[ 72.169469] cleaner_kthread+0x152/0x160 [btrfs]
[ 72.169506] kthread+0x113/0x130
[ 72.169540] ? kthread_create_worker_on_cpu+0x70/0x70
[ 72.169575] ? SyS_exit_group+0x10/0x10
[ 72.169610] ret_from_fork+0x35/0x40
[ 72.169643] Code: 4c 89 f7 45 31 c0 ba 10 00 00 00 4c 89 ee e8 16 23 ff ff 4c 89 f7 e8 9e ef fc ff e9 de fe ff ff 41 bc f4 ff ff ff e9 db fe ff ff <0f> 0b eb b7 e8 85 4c 1a c5 0f 1f 44 00 00 66 66 66 66 90 41 55
[ 72.169705] ---[ end trace ed549af9d9cf6190 ]---
[ 72.170009] WARNING: CPU: 0 PID: 242 at /build/linux-uwVqDp/linux-4.16.16/fs/btrfs/ctree.h:1565 btrfs_update_device+0x1b2/0x1c0 [btrfs]
[ 72.170050] Modules linked in: cpufreq_userspace cpufreq_powersave cpufreq_conservative snd_hda_codec_hdmi ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_policy ipt_REJECT nf_reject_ipv4 xt_comment xt_tcpudp nf_conntrack_ipv4 powernow_k8 nf_defrag_ipv4 edac_mce_amd snd_hda_intel kvm_amd snd_hda_codec ccp rng_core snd_hda_core kvm snd_hwdep irqbypass snd_pcm wmi_bmof radeon snd_timer ttm xt_multiport snd pcspkr soundcore drm_kms_helper k8temp ohci_pci ata_generic pata_atiixp ohci_hcd ehci_pci sg wmi xt_conntrack drm nf_conntrack i2c_algo_bit ehci_hcd usbcore button sp5100_tco usb_common shpchp i2c_piix4 iptable_filter binfmt_misc sunrpc hwmon_vid ip_tables x_tables autofs4 btrfs zstd_decompress zstd_compress xxhash sd_mod raid10 raid456 async_raid6_recov
[ 72.170152] async_memcpy async_pq async_xor async_tx libcrc32c crc32c_generic xor raid6_pq raid1 raid0 multipath linear md_mod evdev ahci libahci serio_raw libata r8169 mii scsi_mod
[ 72.170204] CPU: 0 PID: 242 Comm: btrfs-cleaner Tainted: G W 4.16.0-2-amd64 #1 Debian 4.16.16-2
[ 72.170241] Hardware name: MICRO-STAR INTERNATIONAL CO.,LTD MS-7551/KA780G (MS-7551), BIOS V16.6 05/12/2010
[ 72.170300] RIP: 0010:btrfs_update_device+0x1b2/0x1c0 [btrfs]
[ 72.170333] RSP: 0018:ffffbd5a810a3d60 EFLAGS: 00010206
[ 72.170367] RAX: 0000000000000fff RBX: ffff938e847f8000 RCX: 000000e8a0db1e00
[ 72.170401] RDX: 0000000000001000 RSI: 0000000000003f5c RDI: ffff938e7a8015e0
[ 72.170434] RBP: ffff938e8fb97a00 R08: ffffbd5a810a3d10 R09: ffffbd5a810a3d18
[ 72.170468] R10: 0000000000000003 R11: 0000000000003000 R12: 0000000000000000
[ 72.170501] R13: 0000000000003f3c R14: ffff938e7a8015e0 R15: ffff938e8f0c6328
[ 72.170535] FS: 0000000000000000(0000) GS:ffff938e9dc00000(0000) knlGS:0000000000000000
[ 72.170571] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 72.170604] CR2: 00007fcff92ce000 CR3: 000000020575e000 CR4: 00000000000006f0
[ 72.170638] Call Trace:
[ 72.170696] btrfs_remove_chunk+0x2a9/0x8c0 [btrfs]
[ 72.170751] btrfs_delete_unused_bgs+0x323/0x3f0 [btrfs]
[ 72.170806] ? __btree_submit_bio_start+0x20/0x20 [btrfs]
[ 72.170861] cleaner_kthread+0x152/0x160 [btrfs]
[ 72.170897] kthread+0x113/0x130
[ 72.170930] ? kthread_create_worker_on_cpu+0x70/0x70
[ 72.170966] ? SyS_exit_group+0x10/0x10
[ 72.171000] ret_from_fork+0x35/0x40
[ 72.171033] Code: 4c 89 f7 45 31 c0 ba 10 00 00 00 4c 89 ee e8 16 23 ff ff 4c 89 f7 e8 9e ef fc ff e9 de fe ff ff 41 bc f4 ff ff ff e9 db fe ff ff <0f> 0b eb b7 e8 85 4c 1a c5 0f 1f 44 00 00 66 66 66 66 90 41 55
[ 72.171097] ---[ end trace ed549af9d9cf6191 ]---
[ 967.276408] WARNING: CPU: 0 PID: 242 at /build/linux-uwVqDp/linux-4.16.16/fs/btrfs/ctree.h:1565 btrfs_update_device+0x1b2/0x1c0 [btrfs]
[ 967.276452] Modules linked in: cpufreq_userspace cpufreq_powersave cpufreq_conservative snd_hda_codec_hdmi ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_policy ipt_REJECT nf_reject_ipv4 xt_comment xt_tcpudp nf_conntrack_ipv4 powernow_k8 nf_defrag_ipv4 edac_mce_amd snd_hda_intel kvm_amd snd_hda_codec ccp rng_core snd_hda_core kvm snd_hwdep irqbypass snd_pcm wmi_bmof radeon snd_timer ttm xt_multiport snd pcspkr soundcore drm_kms_helper k8temp ohci_pci ata_generic pata_atiixp ohci_hcd ehci_pci sg wmi xt_conntrack drm nf_conntrack i2c_algo_bit ehci_hcd usbcore button sp5100_tco usb_common shpchp i2c_piix4 iptable_filter binfmt_misc sunrpc hwmon_vid ip_tables x_tables autofs4 btrfs zstd_decompress zstd_compress xxhash sd_mod raid10 raid456 async_raid6_recov
[ 967.276554] async_memcpy async_pq async_xor async_tx libcrc32c crc32c_generic xor raid6_pq raid1 raid0 multipath linear md_mod evdev ahci libahci serio_raw libata r8169 mii scsi_mod
[ 967.276606] CPU: 0 PID: 242 Comm: btrfs-cleaner Tainted: G W 4.16.0-2-amd64 #1 Debian 4.16.16-2
[ 967.276642] Hardware name: MICRO-STAR INTERNATIONAL CO.,LTD MS-7551/KA780G (MS-7551), BIOS V16.6 05/12/2010
[ 967.276703] RIP: 0010:btrfs_update_device+0x1b2/0x1c0 [btrfs]
[ 967.276737] RSP: 0018:ffffbd5a810a3d60 EFLAGS: 00010206
[ 967.276771] RAX: 0000000000000fff RBX: ffff938de01509a0 RCX: 000000e8a0db1e00
[ 967.276804] RDX: 0000000000001000 RSI: 0000000000003f5c RDI: ffff938e177fc7a8
[ 967.276838] RBP: ffff938e8fb97a00 R08: ffffbd5a810a3d10 R09: ffffbd5a810a3d18
[ 967.276872] R10: 0000000000000003 R11: 0000000000003000 R12: 0000000000000000
[ 967.276906] R13: 0000000000003f3c R14: ffff938e177fc7a8 R15: ffff938e8f0c6328
[ 967.276940] FS: 0000000000000000(0000) GS:ffff938e9dc00000(0000) knlGS:0000000000000000
[ 967.276976] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 967.277010] CR2: 0000563538320878 CR3: 00000002114dc000 CR4: 00000000000006f0
[ 967.277044] Call Trace:
[ 967.277104] btrfs_remove_chunk+0x2a9/0x8c0 [btrfs]
[ 967.277161] btrfs_delete_unused_bgs+0x323/0x3f0 [btrfs]
[ 967.277217] ? __btree_submit_bio_start+0x20/0x20 [btrfs]
[ 967.277272] cleaner_kthread+0x152/0x160 [btrfs]
[ 967.277310] kthread+0x113/0x130
[ 967.277344] ? kthread_create_worker_on_cpu+0x70/0x70
[ 967.277379] ? SyS_exit_group+0x10/0x10
[ 967.277414] ret_from_fork+0x35/0x40
[ 967.277447] Code: 4c 89 f7 45 31 c0 ba 10 00 00 00 4c 89 ee e8 16 23 ff ff 4c 89 f7 e8 9e ef fc ff e9 de fe ff ff 41 bc f4 ff ff ff e9 db fe ff ff <0f> 0b eb b7 e8 85 4c 1a c5 0f 1f 44 00 00 66 66 66 66 90 41 55
[ 967.277510] ---[ end trace ed549af9d9cf6192 ]---
[ 967.277747] WARNING: CPU: 0 PID: 242 at /build/linux-uwVqDp/linux-4.16.16/fs/btrfs/ctree.h:1565 btrfs_update_device+0x1b2/0x1c0 [btrfs]
[ 967.277786] Modules linked in: cpufreq_userspace cpufreq_powersave cpufreq_conservative snd_hda_codec_hdmi ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_policy ipt_REJECT nf_reject_ipv4 xt_comment xt_tcpudp nf_conntrack_ipv4 powernow_k8 nf_defrag_ipv4 edac_mce_amd snd_hda_intel kvm_amd snd_hda_codec ccp rng_core snd_hda_core kvm snd_hwdep irqbypass snd_pcm wmi_bmof radeon snd_timer ttm xt_multiport snd pcspkr soundcore drm_kms_helper k8temp ohci_pci ata_generic pata_atiixp ohci_hcd ehci_pci sg wmi xt_conntrack drm nf_conntrack i2c_algo_bit ehci_hcd usbcore button sp5100_tco usb_common shpchp i2c_piix4 iptable_filter binfmt_misc sunrpc hwmon_vid ip_tables x_tables autofs4 btrfs zstd_decompress zstd_compress xxhash sd_mod raid10 raid456 async_raid6_recov
[ 967.277886] async_memcpy async_pq async_xor async_tx libcrc32c crc32c_generic xor raid6_pq raid1 raid0 multipath linear md_mod evdev ahci libahci serio_raw libata r8169 mii scsi_mod
[ 967.277936] CPU: 0 PID: 242 Comm: btrfs-cleaner Tainted: G W 4.16.0-2-amd64 #1 Debian 4.16.16-2
[ 967.277972] Hardware name: MICRO-STAR INTERNATIONAL CO.,LTD MS-7551/KA780G (MS-7551), BIOS V16.6 05/12/2010
[ 967.278033] RIP: 0010:btrfs_update_device+0x1b2/0x1c0 [btrfs]
[ 967.278066] RSP: 0018:ffffbd5a810a3d60 EFLAGS: 00010206
[ 967.278100] RAX: 0000000000000fff RBX: ffff938de01509a0 RCX: 000000e8a0db1e00
[ 967.278134] RDX: 0000000000001000 RSI: 0000000000003f5c RDI: ffff938e177fc7a8
[ 967.278168] RBP: ffff938e8fb97a00 R08: ffffbd5a810a3d10 R09: ffffbd5a810a3d18
[ 967.278202] R10: 0000000000000003 R11: 0000000000003000 R12: 0000000000000000
[ 967.278236] R13: 0000000000003f3c R14: ffff938e177fc7a8 R15: ffff938e8f0c6328
[ 967.278270] FS: 0000000000000000(0000) GS:ffff938e9dc00000(0000) knlGS:0000000000000000
[ 967.278307] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 967.278340] CR2: 0000563538320878 CR3: 00000002114dc000 CR4: 00000000000006f0
[ 967.278374] Call Trace:
[ 967.278432] btrfs_remove_chunk+0x2a9/0x8c0 [btrfs]
[ 967.278489] btrfs_delete_unused_bgs+0x323/0x3f0 [btrfs]
[ 967.278545] ? __btree_submit_bio_start+0x20/0x20 [btrfs]
[ 967.278600] cleaner_kthread+0x152/0x160 [btrfs]
[ 967.278635] kthread+0x113/0x130
[ 967.278669] ? kthread_create_worker_on_cpu+0x70/0x70
[ 967.278703] ? SyS_exit_group+0x10/0x10
[ 967.278738] ret_from_fork+0x35/0x40
[ 967.278771] Code: 4c 89 f7 45 31 c0 ba 10 00 00 00 4c 89 ee e8 16 23 ff ff 4c 89 f7 e8 9e ef fc ff e9 de fe ff ff 41 bc f4 ff ff ff e9 db fe ff ff <0f> 0b eb b7 e8 85 4c 1a c5 0f 1f 44 00 00 66 66 66 66 90 41 55
[ 967.278836] ---[ end trace ed549af9d9cf6193 ]---
[ 967.279036] WARNING: CPU: 0 PID: 242 at /build/linux-uwVqDp/linux-4.16.16/fs/btrfs/ctree.h:1565 btrfs_update_device+0x1b2/0x1c0 [btrfs]
[ 967.279074] Modules linked in: cpufreq_userspace cpufreq_powersave cpufreq_conservative snd_hda_codec_hdmi ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_policy ipt_REJECT nf_reject_ipv4 xt_comment xt_tcpudp nf_conntrack_ipv4 powernow_k8 nf_defrag_ipv4 edac_mce_amd snd_hda_intel kvm_amd snd_hda_codec ccp rng_core snd_hda_core kvm snd_hwdep irqbypass snd_pcm wmi_bmof radeon snd_timer ttm xt_multiport snd pcspkr soundcore drm_kms_helper k8temp ohci_pci ata_generic pata_atiixp ohci_hcd ehci_pci sg wmi xt_conntrack drm nf_conntrack i2c_algo_bit ehci_hcd usbcore button sp5100_tco usb_common shpchp i2c_piix4 iptable_filter binfmt_misc sunrpc hwmon_vid ip_tables x_tables autofs4 btrfs zstd_decompress zstd_compress xxhash sd_mod raid10 raid456 async_raid6_recov
[ 967.279175] async_memcpy async_pq async_xor async_tx libcrc32c crc32c_generic xor raid6_pq raid1 raid0 multipath linear md_mod evdev ahci libahci serio_raw libata r8169 mii scsi_mod
[ 967.279224] CPU: 0 PID: 242 Comm: btrfs-cleaner Tainted: G W 4.16.0-2-amd64 #1 Debian 4.16.16-2
[ 967.279261] Hardware name: MICRO-STAR INTERNATIONAL CO.,LTD MS-7551/KA780G (MS-7551), BIOS V16.6 05/12/2010
[ 967.279321] RIP: 0010:btrfs_update_device+0x1b2/0x1c0 [btrfs]
[ 967.279355] RSP: 0018:ffffbd5a810a3d60 EFLAGS: 00010206
[ 967.279388] RAX: 0000000000000fff RBX: ffff938de01509a0 RCX: 000000e8a0db1e00
[ 967.279422] RDX: 0000000000001000 RSI: 0000000000003f5c RDI: ffff938e177fc7a8
[ 967.279456] RBP: ffff938e8fb97a00 R08: ffffbd5a810a3d10 R09: ffffbd5a810a3d18
[ 967.280145] R10: 0000000000000003 R11: 0000000000003000 R12: 0000000000000000
[ 967.280169] R13: 0000000000003f3c R14: ffff938e177fc7a8 R15: ffff938e8f0c6328
[ 967.280169] FS: 0000000000000000(0000) GS:ffff938e9dc00000(0000) knlGS:0000000000000000
[ 967.280169] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 967.280169] CR2: 0000563538320878 CR3: 00000002114dc000 CR4: 00000000000006f0
[ 967.280169] Call Trace:
[ 967.280169] btrfs_remove_chunk+0x2a9/0x8c0 [btrfs]
[ 967.280169] btrfs_delete_unused_bgs+0x323/0x3f0 [btrfs]
[ 967.280169] ? __btree_submit_bio_start+0x20/0x20 [btrfs]
[ 967.280169] cleaner_kthread+0x152/0x160 [btrfs]
[ 967.280169] kthread+0x113/0x130
[ 967.280169] ? kthread_create_worker_on_cpu+0x70/0x70
[ 967.280169] ? SyS_exit_group+0x10/0x10
[ 967.280169] ret_from_fork+0x35/0x40
[ 967.280169] Code: 4c 89 f7 45 31 c0 ba 10 00 00 00 4c 89 ee e8 16 23 ff ff 4c 89 f7 e8 9e ef fc ff e9 de fe ff ff 41 bc f4 ff ff ff e9 db fe ff ff <0f> 0b eb b7 e8 85 4c 1a c5 0f 1f 44 00 00 66 66 66 66 90 41 55
[ 967.280169] ---[ end trace ed549af9d9cf6194 ]---
[ 1516.410609] WARNING: CPU: 1 PID: 242 at /build/linux-uwVqDp/linux-4.16.16/fs/btrfs/ctree.h:1565 btrfs_update_device+0x1b2/0x1c0 [btrfs]
[ 1516.410647] Modules linked in: cpufreq_userspace cpufreq_powersave cpufreq_conservative snd_hda_codec_hdmi ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_policy ipt_REJECT nf_reject_ipv4 xt_comment xt_tcpudp nf_conntrack_ipv4 powernow_k8 nf_defrag_ipv4 edac_mce_amd snd_hda_intel kvm_amd snd_hda_codec ccp rng_core snd_hda_core kvm snd_hwdep irqbypass snd_pcm wmi_bmof radeon snd_timer ttm xt_multiport snd pcspkr soundcore drm_kms_helper k8temp ohci_pci ata_generic pata_atiixp ohci_hcd ehci_pci sg wmi xt_conntrack drm nf_conntrack i2c_algo_bit ehci_hcd usbcore button sp5100_tco usb_common shpchp i2c_piix4 iptable_filter binfmt_misc sunrpc hwmon_vid ip_tables x_tables autofs4 btrfs zstd_decompress zstd_compress xxhash sd_mod raid10 raid456 async_raid6_recov
[ 1516.410757] async_memcpy async_pq async_xor async_tx libcrc32c crc32c_generic xor raid6_pq raid1 raid0 multipath linear md_mod evdev ahci libahci serio_raw libata r8169 mii scsi_mod
[ 1516.410826] CPU: 1 PID: 242 Comm: btrfs-cleaner Tainted: G W 4.16.0-2-amd64 #1 Debian 4.16.16-2
[ 1516.410861] Hardware name: MICRO-STAR INTERNATIONAL CO.,LTD MS-7551/KA780G (MS-7551), BIOS V16.6 05/12/2010
[ 1516.410941] RIP: 0010:btrfs_update_device+0x1b2/0x1c0 [btrfs]
[ 1516.410975] RSP: 0018:ffffbd5a810a3d60 EFLAGS: 00010206
[ 1516.411008] RAX: 0000000000000fff RBX: ffff938dbbafd380 RCX: 000000e8a0db1e00
[ 1516.411043] RDX: 0000000000001000 RSI: 0000000000003f5c RDI: ffff938e30d156f8
[ 1516.411076] RBP: ffff938e8fb97a00 R08: ffffbd5a810a3d10 R09: ffffbd5a810a3d18
[ 1516.411110] R10: 0000000000000003 R11: 0000000000003000 R12: 0000000000000000
[ 1516.411144] R13: 0000000000003f3c R14: ffff938e30d156f8 R15: ffff938e8f0c6328
[ 1516.411178] FS: 0000000000000000(0000) GS:ffff938e9dc40000(0000) knlGS:0000000000000000
[ 1516.411214] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 1516.411247] CR2: 00007f2041f7c018 CR3: 00000002114dc000 CR4: 00000000000006e0
[ 1516.411280] Call Trace:
[ 1516.411340] btrfs_remove_chunk+0x2a9/0x8c0 [btrfs]
[ 1516.411396] btrfs_delete_unused_bgs+0x323/0x3f0 [btrfs]
[ 1516.411451] ? __btree_submit_bio_start+0x20/0x20 [btrfs]
[ 1516.411505] cleaner_kthread+0x152/0x160 [btrfs]
[ 1516.411542] kthread+0x113/0x130
[ 1516.411576] ? kthread_create_worker_on_cpu+0x70/0x70
[ 1516.411611] ? SyS_exit_group+0x10/0x10
[ 1516.411646] ret_from_fork+0x35/0x40
[ 1516.411679] Code: 4c 89 f7 45 31 c0 ba 10 00 00 00 4c 89 ee e8 16 23 ff ff 4c 89 f7 e8 9e ef fc ff e9 de fe ff ff 41 bc f4 ff ff ff e9 db fe ff ff <0f> 0b eb b7 e8 85 4c 1a c5 0f 1f 44 00 00 66 66 66 66 90 41 55
[ 1516.411742] ---[ end trace ed549af9d9cf6195 ]---
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: call trace: WARNING: at /build/linux-uwVqDp/linux-4.16.16/fs/btrfs/ctree.h:1565 btrfs_update_device
2018-06-28 13:19 call trace: WARNING: at /build/linux-uwVqDp/linux-4.16.16/fs/btrfs/ctree.h:1565 btrfs_update_device Christoph Anton Mitterer
@ 2018-06-28 13:25 ` Nikolay Borisov
2018-06-28 14:09 ` Qu Wenruo
1 sibling, 0 replies; 9+ messages in thread
From: Nikolay Borisov @ 2018-06-28 13:25 UTC (permalink / raw)
To: Christoph Anton Mitterer, linux-btrfs
On 28.06.2018 16:19, Christoph Anton Mitterer wrote:
> Hey.
>
> On a 4.16.16 kernel with a RAID 1 btrfs I got the following messages
> since today.
>
> Data seems still to be readable (correctly)... and there are no other
> errors (like SATA errors) in the kernel log.
>
> Any idea what these could mean?
It means you have a device, whose size is not aligned to 4k. You can fix
this either by resizing the device to be properly aligned to a 4k
boundary (if you are on x86) or better yet, just run :
btrfs rescue fix-device-size /dev/<device to fix>
>
> Thanks,
> Chris.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: call trace: WARNING: at /build/linux-uwVqDp/linux-4.16.16/fs/btrfs/ctree.h:1565 btrfs_update_device
2018-06-28 13:19 call trace: WARNING: at /build/linux-uwVqDp/linux-4.16.16/fs/btrfs/ctree.h:1565 btrfs_update_device Christoph Anton Mitterer
2018-06-28 13:25 ` Nikolay Borisov
@ 2018-06-28 14:09 ` Qu Wenruo
2018-06-28 14:17 ` Christoph Anton Mitterer
1 sibling, 1 reply; 9+ messages in thread
From: Qu Wenruo @ 2018-06-28 14:09 UTC (permalink / raw)
To: Christoph Anton Mitterer, linux-btrfs
[-- Attachment #1.1: Type: text/plain, Size: 691 bytes --]
On 2018年06月28日 21:19, Christoph Anton Mitterer wrote:
> Hey.
>
> On a 4.16.16 kernel with a RAID 1 btrfs I got the following messages
> since today.
>
> Data seems still to be readable (correctly)... and there are no other
> errors (like SATA errors) in the kernel log.
>
> Any idea what these could mean?
>
> Thanks,
> Chris.
>
>
> [ 72.168662] WARNING: CPU: 0 PID: 242 at /build/linux-uwVqDp/linux-4.16.16/fs/btrfs/ctree.h:1565 btrfs_update_device+0x1b2/0x1c0It looks like it's the old WARN_ON() for unaligned device size.
Would you please verify if it is the case?
If so, "btrfs rescue fix-device-size" should handle it pretty well.
Thanks,
Qu
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: call trace: WARNING: at /build/linux-uwVqDp/linux-4.16.16/fs/btrfs/ctree.h:1565 btrfs_update_device
2018-06-28 14:09 ` Qu Wenruo
@ 2018-06-28 14:17 ` Christoph Anton Mitterer
2018-06-28 14:25 ` Nikolay Borisov
2018-06-28 14:58 ` Qu Wenruo
0 siblings, 2 replies; 9+ messages in thread
From: Christoph Anton Mitterer @ 2018-06-28 14:17 UTC (permalink / raw)
To: Qu Wenruo, linux-btrfs
On Thu, 2018-06-28 at 22:09 +0800, Qu Wenruo wrote:
> > [ 72.168662] WARNING: CPU: 0 PID: 242 at /build/linux-
> > uwVqDp/linux-4.16.16/fs/btrfs/ctree.h:1565
> > btrfs_update_device+0x1b2/0x1c0It
> looks like it's the old WARN_ON() for unaligned device size.
> Would you please verify if it is the case?
# blockdev --getsize64 /dev/sdb2 /dev/sda2
999131127296
999131127296
Since getsize64 returns bytes and not sectors, I suppose it would need
to be aligned to 1024 by the least?
999131127296 / 1024 = 975713991,5
So it's not.
> If so, "btrfs rescue fix-device-size" should handle it pretty well.
I guess this needs to be done with the fs unmounted?
Anything to consider since I have RAID1 (except from running it on both
devices)?
Also, it's a bit strange that this error occurred never before (though
the btrfs-restore manpage says the kernel would check for this since
4.11).
It would further be nice if btrfs-check would warn about this.
Thanks,
Chris.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: call trace: WARNING: at /build/linux-uwVqDp/linux-4.16.16/fs/btrfs/ctree.h:1565 btrfs_update_device
2018-06-28 14:17 ` Christoph Anton Mitterer
@ 2018-06-28 14:25 ` Nikolay Borisov
2018-06-28 14:58 ` Qu Wenruo
1 sibling, 0 replies; 9+ messages in thread
From: Nikolay Borisov @ 2018-06-28 14:25 UTC (permalink / raw)
To: Christoph Anton Mitterer, Qu Wenruo, linux-btrfs
On 28.06.2018 17:17, Christoph Anton Mitterer wrote:
> On Thu, 2018-06-28 at 22:09 +0800, Qu Wenruo wrote:
>>> [ 72.168662] WARNING: CPU: 0 PID: 242 at /build/linux-
>>> uwVqDp/linux-4.16.16/fs/btrfs/ctree.h:1565
>>> btrfs_update_device+0x1b2/0x1c0It
>> looks like it's the old WARN_ON() for unaligned device size.
>> Would you please verify if it is the case?
>
> # blockdev --getsize64 /dev/sdb2 /dev/sda2
> 999131127296
> 999131127296
>
>
> Since getsize64 returns bytes and not sectors, I suppose it would need
> to be aligned to 1024 by the least?
>
> 999131127296 / 1024 = 975713991,5
>
> So it's not.
>
>
>> If so, "btrfs rescue fix-device-size" should handle it pretty well.
>
> I guess this needs to be done with the fs unmounted?
> Anything to consider since I have RAID1 (except from running it on both
> devices)?
>
>
> Also, it's a bit strange that this error occurred never before (though
> the btrfs-restore manpage says the kernel would check for this since
> 4.11).
Was this an old FS or a fresh one? Looking at the callstack this seems
to have occured due to "btrfs_set_device_total_bytes(leaf, dev_item,
btrfs_device_get_disk_total_bytes(device));" call. Meaning the total
bytes of the disk were unalgined. Perhaps this has been like that for
quite some time, then you did a couple of kernel upgrades (this WARN_ON
was added later than 4.11) and just now you happened to delete a chunk
which would trigger a device update on-disk ?
>
> It would further be nice if btrfs-check would warn about this.
>
>
> Thanks,
> Chris.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: call trace: WARNING: at /build/linux-uwVqDp/linux-4.16.16/fs/btrfs/ctree.h:1565 btrfs_update_device
2018-06-28 14:17 ` Christoph Anton Mitterer
2018-06-28 14:25 ` Nikolay Borisov
@ 2018-06-28 14:58 ` Qu Wenruo
2018-06-29 1:05 ` Christoph Anton Mitterer
1 sibling, 1 reply; 9+ messages in thread
From: Qu Wenruo @ 2018-06-28 14:58 UTC (permalink / raw)
To: Christoph Anton Mitterer, linux-btrfs
[-- Attachment #1.1: Type: text/plain, Size: 1366 bytes --]
On 2018年06月28日 22:17, Christoph Anton Mitterer wrote:
> On Thu, 2018-06-28 at 22:09 +0800, Qu Wenruo wrote:
>>> [ 72.168662] WARNING: CPU: 0 PID: 242 at /build/linux-
>>> uwVqDp/linux-4.16.16/fs/btrfs/ctree.h:1565
>>> btrfs_update_device+0x1b2/0x1c0It
>> looks like it's the old WARN_ON() for unaligned device size.
>> Would you please verify if it is the case?
>
> # blockdev --getsize64 /dev/sdb2 /dev/sda2
> 999131127296
> 999131127296
>
>
> Since getsize64 returns bytes and not sectors, I suppose it would need
> to be aligned to 1024 by the least?
>
> 999131127296 / 1024 = 975713991,5
>
> So it's not.
So it's the case.
>
>
>> If so, "btrfs rescue fix-device-size" should handle it pretty well.
>
> I guess this needs to be done with the fs unmounted?
Yep.
> Anything to consider since I have RAID1 (except from running it on both
> devices)?
Nothing special. Btrfs-progs will handle it pretty well.
>
>
> Also, it's a bit strange that this error occurred never before (though
> the btrfs-restore manpage says the kernel would check for this since
> 4.11).
Because the WARN_ON() is newly added.
>
> It would further be nice if btrfs-check would warn about this.
Yep, latest will warn about it, and --repair can also fix it too.
Thanks,
Qu
>
>
> Thanks,
> Chris.
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: call trace: WARNING: at /build/linux-uwVqDp/linux-4.16.16/fs/btrfs/ctree.h:1565 btrfs_update_device
2018-06-28 14:58 ` Qu Wenruo
@ 2018-06-29 1:05 ` Christoph Anton Mitterer
2018-06-29 1:10 ` Qu Wenruo
0 siblings, 1 reply; 9+ messages in thread
From: Christoph Anton Mitterer @ 2018-06-29 1:05 UTC (permalink / raw)
To: linux-btrfs; +Cc: Nikolay Borisov, Qu Wenruo
Hey Qu and Nikolay.
On Thu, 2018-06-28 at 22:58 +0800, Qu Wenruo wrote:
> Nothing special. Btrfs-progs will handle it pretty well.
Since this a remote system where the ISP provides only a rescue image
with pretty old kernel/btrfs-progs, I had to copy a current local
binary and use that... but that seemed to have worked quite well
> Because the WARN_ON() is newly added.
Ah I see.
> Yep, latest will warn about it, and --repair can also fix it too.
Great.
On Thu, 2018-06-28 at 17:25 +0300, Nikolay Borisov wrote:
> Was this an old FS or a fresh one?
You mean in terms of original fs creation? Probably rather oldish.. I'd
guess at least a year or maybe even 2-3 or more.
> Looking at the callstack this
> seems
> to have occured due to "btrfs_set_device_total_bytes(leaf, dev_item,
> btrfs_device_get_disk_total_bytes(device));" call. Meaning the total
> bytes of the disk were unalgined. Perhaps this has been like that for
> quite some time, then you did a couple of kernel upgrades (this
> WARN_ON
> was added later than 4.11) and just now you happened to delete a
> chunk
> which would trigger a device update on-disk ?
Could be...
The following was however still a bit strange:
sda2 and sdb2 are the partitions on the two HDDs forming the RAID1.
root@rescue ~ # ./btrfs rescue fix-device-size /dev/sda2
Fixed device size for devid 2, old size: 999131127296 new size: 999131123712
Fixed super total bytes, old size: 1998262251008 new size: 1998262247424
Fixed unaligned/mismatched total_bytes for super block and device items
root@rescue ~ # ./btrfs rescue fix-device-size /dev/sdb2
No device size related problem found
As you can see, no alignment issues were found on sdb2.
I've created these at the same time...
I don't think (but cannot exclude for 100%) that this server ever lost
a disk (in that case I could image that newer progs/kernel might have
created sdb2 with proper alignment)
Looking at the partitions:
root@rescue ~ # gdisk -l /dev/sda
GPT fdisk (gdisk) version 1.0.1
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 1953525168 sectors, 931.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID):
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)
Number Start (sector) End (sector) Size Code Name
1 2048 2097151 1023.0 MiB EF02 BIOS boot partition
2 2097152 1953525134 930.5 GiB 8300 Linux filesystem
root@rescue ~ # gdisk -l /dev/sdb
GPT fdisk (gdisk) version 1.0.1
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sdb: 1953525168 sectors, 931.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID):
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)
Number Start (sector) End (sector) Size Code Name
1 2048 2097151 1023.0 MiB EF02 BIOS boot partition
2 2097152 1953525134 930.5 GiB 8300 Linux filesystem
Both the same... so if there was no device replace or so... then I
wonder why only one device was affected.
Cheers,
Chris.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: call trace: WARNING: at /build/linux-uwVqDp/linux-4.16.16/fs/btrfs/ctree.h:1565 btrfs_update_device
2018-06-29 1:05 ` Christoph Anton Mitterer
@ 2018-06-29 1:10 ` Qu Wenruo
2018-06-29 12:55 ` Christoph Anton Mitterer
0 siblings, 1 reply; 9+ messages in thread
From: Qu Wenruo @ 2018-06-29 1:10 UTC (permalink / raw)
To: Christoph Anton Mitterer, linux-btrfs; +Cc: Nikolay Borisov
On 2018年06月29日 09:05, Christoph Anton Mitterer wrote:
> Hey Qu and Nikolay.
>
>
> On Thu, 2018-06-28 at 22:58 +0800, Qu Wenruo wrote:
>> Nothing special. Btrfs-progs will handle it pretty well.
> Since this a remote system where the ISP provides only a rescue image
> with pretty old kernel/btrfs-progs, I had to copy a current local
> binary and use that... but that seemed to have worked quite well
Glad that works.
Just forgot to mention, if it's only device size unalignment while the
super block total_bytes is still accurate, you could just modify it
on-line, using "btrfs fi resize"
Just like
# btrfs fi resize 1:-4K <mnt>
Then it should fix device size unalignment.
>
>> Because the WARN_ON() is newly added.
> Ah I see.
>
>> Yep, latest will warn about it, and --repair can also fix it too.
> Great.
>
>
> On Thu, 2018-06-28 at 17:25 +0300, Nikolay Borisov wrote:
>> Was this an old FS or a fresh one?
> You mean in terms of original fs creation? Probably rather oldish.. I'd
> guess at least a year or maybe even 2-3 or more.
>
>> Looking at the callstack this
>> seems
>> to have occured due to "btrfs_set_device_total_bytes(leaf, dev_item,
>> btrfs_device_get_disk_total_bytes(device));" call. Meaning the total
>> bytes of the disk were unalgined. Perhaps this has been like that for
>> quite some time, then you did a couple of kernel upgrades (this
>> WARN_ON
>> was added later than 4.11) and just now you happened to delete a
>> chunk
>> which would trigger a device update on-disk ?
> Could be...
>
>
> The following was however still a bit strange:
> sda2 and sdb2 are the partitions on the two HDDs forming the RAID1.
>
>
> root@rescue ~ # ./btrfs rescue fix-device-size /dev/sda2
> Fixed device size for devid 2, old size: 999131127296 new size: 999131123712
> Fixed super total bytes, old size: 1998262251008 new size: 1998262247424
> Fixed unaligned/mismatched total_bytes for super block and device items
> root@rescue ~ # ./btrfs rescue fix-device-size /dev/sdb2
> No device size related problem found
>
> As you can see, no alignment issues were found on sdb2.
>
> I've created these at the same time...
> I don't think (but cannot exclude for 100%) that this server ever lost
> a disk (in that case I could image that newer progs/kernel might have
> created sdb2 with proper alignment)
>
> Looking at the partitions:
>
> root@rescue ~ # gdisk -l /dev/sda
> GPT fdisk (gdisk) version 1.0.1
>
> Partition table scan:
> MBR: protective
> BSD: not present
> APM: not present
> GPT: present
>
> Found valid GPT with protective MBR; using GPT.
> Disk /dev/sda: 1953525168 sectors, 931.5 GiB
> Logical sector size: 512 bytes
> Disk identifier (GUID):
> Partition table holds up to 128 entries
> First usable sector is 34, last usable sector is 1953525134
> Partitions will be aligned on 2048-sector boundaries
> Total free space is 2014 sectors (1007.0 KiB)
>
> Number Start (sector) End (sector) Size Code Name
> 1 2048 2097151 1023.0 MiB EF02 BIOS boot partition
> 2 2097152 1953525134 930.5 GiB 8300 Linux filesystem
> root@rescue ~ # gdisk -l /dev/sdb
> GPT fdisk (gdisk) version 1.0.1
>
> Partition table scan:
> MBR: protective
> BSD: not present
> APM: not present
> GPT: present
>
> Found valid GPT with protective MBR; using GPT.
> Disk /dev/sdb: 1953525168 sectors, 931.5 GiB
> Logical sector size: 512 bytes
> Disk identifier (GUID):
> Partition table holds up to 128 entries
> First usable sector is 34, last usable sector is 1953525134
> Partitions will be aligned on 2048-sector boundaries
> Total free space is 2014 sectors (1007.0 KiB)
>
> Number Start (sector) End (sector) Size Code Name
> 1 2048 2097151 1023.0 MiB EF02 BIOS boot partition
> 2 2097152 1953525134 930.5 GiB 8300 Linux filesystem
>
>
> Both the same... so if there was no device replace or so... then I
> wonder why only one device was affected.
Maybe it's the old mkfs causing the problem?
Although mkfs.btrfs added device size alignment much earlier than
kernel, it's still possible that the old mkfs doesn't handle the initial
device and extra device (mkfs.btrfs will always create a temporary fs on
the first device, then add all the other devices to the system) the same
way.
Thanks,
Qu
>
>
> Cheers,
> Chris.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: call trace: WARNING: at /build/linux-uwVqDp/linux-4.16.16/fs/btrfs/ctree.h:1565 btrfs_update_device
2018-06-29 1:10 ` Qu Wenruo
@ 2018-06-29 12:55 ` Christoph Anton Mitterer
0 siblings, 0 replies; 9+ messages in thread
From: Christoph Anton Mitterer @ 2018-06-29 12:55 UTC (permalink / raw)
To: Qu Wenruo, linux-btrfs; +Cc: Nikolay Borisov
On Fri, 2018-06-29 at 09:10 +0800, Qu Wenruo wrote:
> Maybe it's the old mkfs causing the problem?
> Although mkfs.btrfs added device size alignment much earlier than
> kernel, it's still possible that the old mkfs doesn't handle the
> initial
> device and extra device (mkfs.btrfs will always create a temporary fs
> on
> the first device, then add all the other devices to the system) the
> same
> way.
Well who knows,.. at least now everything's fine again :-)
Thanks guys!
Chris.
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2018-06-29 12:55 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-06-28 13:19 call trace: WARNING: at /build/linux-uwVqDp/linux-4.16.16/fs/btrfs/ctree.h:1565 btrfs_update_device Christoph Anton Mitterer
2018-06-28 13:25 ` Nikolay Borisov
2018-06-28 14:09 ` Qu Wenruo
2018-06-28 14:17 ` Christoph Anton Mitterer
2018-06-28 14:25 ` Nikolay Borisov
2018-06-28 14:58 ` Qu Wenruo
2018-06-29 1:05 ` Christoph Anton Mitterer
2018-06-29 1:10 ` Qu Wenruo
2018-06-29 12:55 ` Christoph Anton Mitterer
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.