From: Kenny MacDermid <kenny.macdermid@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: input/output errors on btrfs-luks-lvm
Date: Wed, 13 Jan 2016 22:22:30 -0400 [thread overview]
Message-ID: <20160114022227.GA18911@gmail.com> (raw)
Hello,
I'm running kernel 4.3.3-2-ARCH, and I sometimes get 'Input/output
error' when trying to access files.
I haven't found any logs as to why, and nothing appears in dmesg.
I'm running in a subvolume on an encrypted fs running on lvm.
I've tried a scrub, which has worked before , but no luck. I could try a
reboot, but I wanted to see if there's any other suggestions first.
$ stat ./script
File: ‘./script’
Size: 142401 Blocks: 280 IO Block: 4096 regular file
Device: 2bh/43d Inode: 1251585 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 1000/ kenny) Gid: ( 1000/ kenny)
Access: 2016-01-13 20:16:43.308699108 -0400
Modify: 2016-01-06 21:12:02.756840023 -0400
Change: 2016-01-06 21:12:02.756840023 -0400
# btrfs inspect-internal inode-resolve -v 1251585 ./
ioctl ret=0, bytes_left=4047, bytes_missing=0, cnt=1, missed=0
reply other threads:[~2016-01-14 2:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160114022227.GA18911@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).