linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kenny MacDermid <kenny.macdermid@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Input/Output errors
Date: Tue, 23 Feb 2016 20:40:46 -0400	[thread overview]
Message-ID: <20160224004045.GA20632@gmail.com> (raw)

I'm running btrfs on DM-Crypt Luks running on LVM.

Occasionally I get files that are unreadable for some period of time.
Attempting to read from them results in an 

Input/output error

Sometimes they'll come back on their own, and sometimes a scrub seems to
help, but sometimes I just have to delete them.

Nothing shows up in dmesg when these occur, and I can't predict which
files it will be, or what causes it.

It's currently happening running 4.4.1-2-ARCH, but I've seen the same
thing for many previous kernel versions.

Does anyone have any suggestions?


             reply	other threads:[~2016-02-24  0:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24  0:40 Kenny MacDermid [this message]
2016-02-24  1:56 ` Input/Output errors Marc MERLIN
2016-02-24  3:02   ` Kenny MacDermid
2016-02-24  4:37     ` Chris Murphy
2016-02-24  8:58       ` Szalma László
2016-02-24 18:13         ` Kenny MacDermid
2016-02-24 18:02       ` Kenny MacDermid

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=20160224004045.GA20632@gmail.com \
    --to=kenny.macdermid@gmail.com \
    --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).