linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: "Piotr Pawłow" <btrfs@pp.siedziba.pl>, linux-btrfs@vger.kernel.org
Subject: Re: kernel BUG at /build/linux-H5UzH8/linux-4.10.0/fs/btrfs/extent_io.c:2318
Date: Fri, 11 Aug 2017 07:40:28 -0400	[thread overview]
Message-ID: <279e40dc-aec3-a208-73f9-effc53da2774@gmail.com> (raw)
In-Reply-To: <ee99ff49-ea05-da8d-6a77-fe3f60b8c154@siedziba.pl>

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!


      reply	other threads:[~2017-08-11 11:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-07 13:26 kernel BUG at /build/linux-H5UzH8/linux-4.10.0/fs/btrfs/extent_io.c:2318 Piotr Pawłow
2017-08-07 22:24 ` Duncan
2017-08-11  9:57   ` Piotr Pawłow
2017-08-11 11:40     ` Austin S. Hemmelgarn [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=279e40dc-aec3-a208-73f9-effc53da2774@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=btrfs@pp.siedziba.pl \
    --cc=linux-btrfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).