All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Seeger <philip@philip-seeger.de>
To: Chris Murphy <lists@colorremedies.com>, linux-btrfs@vger.kernel.org
Subject: Re: Monitoring not working as "dev stats" returns 0 after read error occurred
Date: Thu, 09 Jan 2020 11:49:35 +0100	[thread overview]
Message-ID: <938be4dc21140fc54a0f318ab26c3d9d@philip-seeger.de> (raw)
In-Reply-To: <CAJCQCtQ-+h36QgOk5ZohLdNwEhzWwqpU=ZjsGXnDLNAPTmwv1w@mail.gmail.com>

On 2020-01-08 22:47, Chris Murphy wrote:
> Unrelated to your report, but you need to update your kernel. The one
> you're using has a pernicious bug that can result in unrepairable
> corruption of the file system. Use 5.2.15 or newer.
> 
> https://lore.kernel.org/linux-btrfs/20190725082729.14109-3-nborisov@suse.com/

Chris, thank you very much! I appreciate it (not the pernicious bug but 
the heads-up).

I was going to do that anyway very soon.

I guess those who're not always up-to-date with their kernel are living 
dangerous lives...
(I just realized that I still wouldn't know about that bad drive, had I 
upgraded or rebooted earlier.)

  reply	other threads:[~2020-01-09 10:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-08 17:41 Monitoring not working as "dev stats" returns 0 after read error occurred philip
2020-01-08 19:35 ` Graham Cobb
2020-01-09 10:33   ` Philip Seeger
2020-01-09 12:04     ` Nikolay Borisov
2020-01-09 14:34       ` Philip Seeger
2020-01-09 23:50         ` Philip Seeger
2020-01-11  7:42           ` Andrei Borzenkov
2020-01-12 11:42             ` Philip Seeger
2020-01-12 17:39               ` waxhead
2020-01-12 20:27                 ` Chris Murphy
2020-01-12 22:45                 ` Philip Seeger
2020-01-08 21:47 ` Chris Murphy
2020-01-09 10:49   ` Philip Seeger [this message]
2020-01-16  1:16 ` Zygo Blaxell

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=938be4dc21140fc54a0f318ab26c3d9d@philip-seeger.de \
    --to=philip@philip-seeger.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    /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 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.