Re: kernel BUG at /build/linux-H5UzH8/linux-4.10.0/fs/btrfs/extent_io.c:2318
On 2017-08-11 05:57, Piotr Pawłow wrote: Hello, So 4.10 isn't /too/ far out of range yet, but I'd strongly consider upgrading (or downgrading to 4.9 LTS) as soon as it's reasonably convenient, before 4.13 in any case. Unless you prefer to go the distro support route, of course. I used to stick to latest kernels back when btrfs wasn't as stable and there were frequently important bug fixes. Nowadays I had no problems since such a long time, that I forgot to change the kernel after upgrading the distro. Besides, I thought RAID-1 was stable years ago (except the degraded mount issue). So, just my thoughts on this in particular. Either you are staying absolutely up to date (which I would still recommend if possible, there are new fixes going in regularly still, and we've been seing some performance improvements recently too), or you're not. If you're not, you should either: 1. Stick to upstream (kernel.org) LTS releases (and still ideally stay up to date within that release) and get reasonably reliable help from the ML. 2. Stick to your distribution's kernels, and get help from your distribution's usual support channels. As far as raid1 mode, it generally is reasonably stable, but there are still edge cases we with bugs that haven't been found (as you found out here). Anyway, after I took care of bad blocks by remapping them, scrub fixed all corruptions without any problems. Fsck comes out clean and everything seems fine. Glad to hear everything is working now! -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: kernel BUG at /build/linux-H5UzH8/linux-4.10.0/fs/btrfs/extent_io.c:2318
Hello, > So 4.10 isn't /too/ far out of range yet, but I'd strongly consider > upgrading (or downgrading to 4.9 LTS) as soon as it's reasonably > convenient, before 4.13 in any case. Unless you prefer to go the > distro support route, of course. I used to stick to latest kernels back when btrfs wasn't as stable and there were frequently important bug fixes. Nowadays I had no problems since such a long time, that I forgot to change the kernel after upgrading the distro. Besides, I thought RAID-1 was stable years ago (except the degraded mount issue). Anyway, after I took care of bad blocks by remapping them, scrub fixed all corruptions without any problems. Fsck comes out clean and everything seems fine. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: kernel BUG at /build/linux-H5UzH8/linux-4.10.0/fs/btrfs/extent_io.c:2318
Piotr Pawłow posted on Mon, 07 Aug 2017 15:26:16 +0200 as excerpted: > # uname -a > Linux pps 4.10.0-30-generic #34-Ubuntu SMP > Mon Jul 31 19:38:17 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux This is a general principles reply and chances are wouldn't help with your issue since the spread isn't /too/ large yet and I've no knowledge of a specific fix for your issue in newer kernels, but FWIW... This being the btrfs development list and btrfs, while stabilizing (but not yet to be considered fully stable) still being under rather intense development, with significant changes every kernel cycle, list focus tends to be quite forward looking, with most interest and the best chance of fixes on relatively current kernels. What we try to support, in addition to development kernels, is the latest two release kernel series in two tracks, (mainline/Linus) current and LTS. On the current track, 4.12 is the newest release so 4.12 and 4.11 are best supported, tho the 4.11 series is already listed as EOL on kernel.org. On the LTS track, 4.9 and 4.4 are the latest LTS releases, with 4.1 the previous one but already well out of btrfs focus range. That puts 4.10 out of the list's best-supported focus range, with 4.11 still in focus but EOL. Beyond that we still try, but you're not as likely to get interest from the developers themselves, and for the other btrfs-user-regulars here, as the spread gets wider, the support gets more difficult as it's harder to remember where things were back then. So the recommendation would be to either upgrade to 4.12 current if you want to stay on current track, or downgrade to the latest 4.9 release if you prefer stable track. Other alternatives would include getting support from your distro if you're running a distro kernel (as seems to be your case), since they know what they've backported and what they haven't, and are thus in a better position to support it, and of course, simply sticking with what you have and accepting that you won't get quite the support or interest on your list posts since you're out of primary focus range. Of course you can also keep a current kernel available and boot to it to try to duplicate any issues before reporting, while otherwise sticking to your older kernel, but unless you have a specific reason to do that, it would seem more trouble than simply running the current kernel by default. So 4.10 isn't /too/ far out of range yet, but I'd strongly consider upgrading (or downgrading to 4.9 LTS) as soon as it's reasonably convenient, before 4.13 in any case. Unless you prefer to go the distro support route, of course. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
kernel BUG at /build/linux-H5UzH8/linux-4.10.0/fs/btrfs/extent_io.c:2318
stripe_index=2176876031, num_stripes=2 sie 07 04:45:06 pps kernel: BTRFS critical (device dm-1): stripe index math went horribly wrong, got stripe_index=2176876031, num_stripes=2 sie 07 04:45:06 pps kernel: BTRFS critical (device dm-1): stripe index math went horribly wrong, got stripe_index=2176876031, num_stripes=2 sie 07 04:45:06 pps kernel: BTRFS critical (device dm-1): stripe index math went horribly wrong, got stripe_index=2176876031, num_stripes=2 sie 07 04:45:06 pps kernel: BTRFS critical (device dm-1): stripe index math went horribly wrong, got stripe_index=2176876031, num_stripes=2 sie 07 04:45:06 pps kernel: BTRFS critical (device dm-1): stripe index math went horribly wrong, got stripe_index=2176876031, num_stripes=2 sie 07 04:45:06 pps kernel: BTRFS critical (device dm-1): stripe index math went horribly wrong, got stripe_index=2176876031, num_stripes=2 sie 07 04:45:06 pps kernel: BTRFS critical (device dm-1): stripe index math went horribly wrong, got stripe_index=2176876031, num_stripes=2 sie 07 04:45:06 pps kernel: BTRFS critical (device dm-1): stripe index math went horribly wrong, got stripe_index=2176876031, num_stripes=2 sie 07 04:45:06 pps kernel: BTRFS critical (device dm-1): stripe index math went horribly wrong, got stripe_index=2176876031, num_stripes=2 sie 07 04:45:06 pps kernel: BTRFS critical (device dm-1): stripe index math went horribly wrong, got stripe_index=2176876031, num_stripes=2 sie 07 04:45:06 pps kernel: BTRFS critical (device dm-1): stripe index math went horribly wrong, got stripe_index=2176876031, num_stripes=2 sie 07 04:45:06 pps kernel: BTRFS critical (device dm-1): stripe index math went horribly wrong, got stripe_index=2176876031, num_stripes=2 sie 07 04:45:06 pps kernel: BTRFS critical (device dm-1): stripe index math went horribly wrong, got stripe_index=2176876031, num_stripes=2 sie 07 04:45:06 pps kernel: BTRFS critical (device dm-1): stripe index math went horribly wrong, got stripe_index=2176876031, num_stripes=2 sie 07 04:45:06 pps kernel: BTRFS critical (device dm-1): stripe index math went horribly wrong, got stripe_index=2176876031, num_stripes=2 sie 07 04:45:06 pps kernel: BTRFS critical (device dm-1): stripe index math went horribly wrong, got stripe_index=2176876031, num_stripes=2 sie 07 04:45:06 pps kernel: BTRFS critical (device dm-1): stripe index math went horribly wrong, got stripe_index=2176876031, num_stripes=2 sie 07 04:45:06 pps kernel: BTRFS critical (device dm-1): stripe index math went horribly wrong, got stripe_index=2176876031, num_stripes=2 sie 07 04:45:06 pps kernel: BTRFS critical (device dm-1): stripe index math went horribly wrong, got stripe_index=2176876031, num_stripes=2 sie 07 04:45:06 pps kernel: BTRFS critical (device dm-1): stripe index math went horribly wrong, got stripe_index=2176876031, num_stripes=2 sie 07 04:45:06 pps kernel: BTRFS critical (device dm-1): stripe index math went horribly wrong, got stripe_index=2176876031, num_stripes=2 sie 07 04:45:06 pps kernel: BTRFS critical (device dm-1): stripe index math went horribly wrong, got stripe_index=2176876031, num_stripes=2 sie 07 04:45:06 pps kernel: BTRFS critical (device dm-1): stripe index math went horribly wrong, got stripe_index=2176876031, num_stripes=2 sie 07 04:45:06 pps kernel: BTRFS info (device dm-1): csum failed ino 1340360 extent 5370531217408 csum 716315696 wanted 722897355 mirror -2118091264 sie 07 04:45:06 pps kernel: kernel BUG at /build/linux-H5UzH8/linux-4.10.0/fs/btrfs/extent_io.c:2318! sie 07 04:45:06 pps kernel: invalid opcode: [#1] SMP sie 07 04:45:06 pps kernel: Modules linked in: xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_tcpudp bridge stp llc ip6table_filter ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6_tables iptable_filter iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_mangle binfmt_misc intel_rapl intel_soc_dts_iosf intel_powerclamp ppdev coretemp kvm_intel snd_soc_rt5670 snd_intel_sst_acpi snd_soc_rt5645 kvm snd_intel_sst_core snd_soc_sst_mfld_platform snd_hda_codec_hdmi irqbypass snd_hda_codec_realtek snd_hda_codec_generic snd_soc_rt5640 punit_atom_debug snd_soc_sst_match crct10dif_pclmul crc32_pclmul snd_soc_rl6231 ghash_clmulni_intel snd_soc_core snd_hda_intel cryptd snd_hda_codec snd_compress snd_hda_core ac97_bus intel_cstate snd_pcm_dmaengine sie 07 04:45:06 pps kernel: snd_hwdep hci_uart btbcm btqca btintel snd_pcm lpc_ich dw_dmac bluetooth rfkill_gpio 8250_dw dw_dmac_core spi_pxa2xx_platform parport_pc snd_timer snd pwm_lpss_platform mac_hid parport mei_txe mei soundcore i2c_designware_platform i2c_designware_core pwm_lpss shpchp sunrpc w83627ehf hwmon_vid ip_tables x_tables autofs4 btrfs xor raid6_pq 9pnet_virtio 9p 9pnet fscache uas usb_storage i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops r8169 drm mii ahci libahci video fjes i2c_hid hid sdhci_acpi sdhci sie 07
