linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Chant <pete@petezilla.co.uk>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Chasing IO errors. BTRFS: error (device dm-2) in btrfs_run_delayed_refs:2907: errno=-5 IO failure
Date: Wed, 21 Aug 2019 00:47:00 +0100	[thread overview]
Message-ID: <1359d6d8-38a4-14d4-ddb1-1de64cd29c19@petezilla.co.uk> (raw)
In-Reply-To: <CAJCQCtSWi+PUbOWXNwv0guCLRuSgZunWdvRBB4TKMG_X48jHFw@mail.gmail.com>

On 8/20/19 10:59 PM, Chris Murphy wrote:
> On Tue, Aug 20, 2019 at 3:10 PM Peter Chant <pete@petezilla.co.uk> wrote:
>>
>> Chasing IO errors.  BTRFS: error (device dm-2) in
>> btrfs_run_delayed_refs:2907: errno=-5 IO failure
>>
>>
>> I've just had an odd one.
>>
>> Over the last few days I've noticed a file system blocking, if that is
>> the correct term, and this morning go read only.  This resulted in a lot
>> of checksum errors.
> 
> That doesn't sound good. Checksum errors where? A complete start to
> finish dmesg is most useful in this case.
> 

I've just booted, degraded, and the file system went readonly quickly.
Is it good to post the dmesg to here, it is 1341 lines?  I can do it
with all disks if that helps?  (or I could run it through grep, but I
suspect there is good reason for not doing that.)

I'll look at the sysrq stuff, but I'm not likely to hit that right this
moment as the system is not really usable in this state and I'm assuming
I'll do more harm than good soldiering on.

Can't do anything with the systemd stuff as I'm running slackware which
does not use it.

Also, this is really bad timing, so although I can do stuff with the
system for the next day or two I'll need to step away from it for a
short while.

Thank you,

Pete

  reply	other threads:[~2019-08-20 22:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-20 20:36 Chasing IO errors. BTRFS: error (device dm-2) in btrfs_run_delayed_refs:2907: errno=-5 IO failure Peter Chant
2019-08-20 21:59 ` Chris Murphy
2019-08-20 23:47   ` Peter Chant [this message]
2019-08-21  8:05   ` Peter Chant
2019-08-21  7:29     ` Qu Wenruo
2019-08-21 21:38       ` Peter Chant
2019-08-21 23:32         ` Qu Wenruo
2019-09-08  7:14           ` Pete
2019-08-20 23:45 ` Qu Wenruo

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=1359d6d8-38a4-14d4-ddb1-1de64cd29c19@petezilla.co.uk \
    --to=pete@petezilla.co.uk \
    --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 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).