From: Marc MERLIN <marc@merlins.org>
To: Kenny MacDermid <kenny.macdermid@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Input/Output errors
Date: Tue, 23 Feb 2016 17:56:58 -0800 [thread overview]
Message-ID: <20160224015658.GY22487@merlins.org> (raw)
In-Reply-To: <20160224004045.GA20632@gmail.com>
On Tue, Feb 23, 2016 at 08:40:46PM -0400, Kenny MacDermid wrote:
> 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?
That's weird to say the least, you should at least get *something* in
dmesg.
And you are getting other error messages and btrfs kernel messages in
your logs?
When whatever app you have that's trying to read them fails, I assume
they also fail with cat or less?
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
next prev parent reply other threads:[~2016-02-24 1:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 0:40 Input/Output errors Kenny MacDermid
2016-02-24 1:56 ` Marc MERLIN [this message]
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=20160224015658.GY22487@merlins.org \
--to=marc@merlins.org \
--cc=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).