From: Diego Calleja <diegocg@gmail.com>
To: Nikolaus Rath <Nikolaus@rath.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Input/output error on newly created file
Date: Thu, 12 May 2016 18:17:50 +0200 [thread overview]
Message-ID: <58549996.M9MX6vESn9@archlinux> (raw)
In-Reply-To: <87eg971dqf.fsf@thinkpad.rath.org>
El jueves, 12 de mayo de 2016 8:46:00 (CEST) Nikolaus Rath escribió:
> *ping*
>
> Anyone any idea?
All I can say is that I've had the same problem in the past. In my
case, the problematic files where active torrents. The interesting
thing is that I was able to read them correctly up to a point, then
I would get the same error as you. No messages in dmesg. The amount
of data I was able to read from them was not random, it was
something multiple of 4K. After reboot the problems went away and
I wasn't able to reproduce it.
There has been reports of similiar issues in the past:
http://www.spinics.net/lists/linux-btrfs/msg52371.html
next prev parent reply other threads:[~2016-05-12 16:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-08 22:18 Input/output error on newly created file Nikolaus Rath
2016-05-09 15:46 ` Filipe Manana
2016-05-10 3:29 ` Nikolaus Rath
2016-05-12 15:46 ` Nikolaus Rath
2016-05-12 16:17 ` Diego Calleja [this message]
2016-05-12 17:41 ` Nikolaus Rath
2016-05-12 18:28 ` Szalma László
2016-05-13 7:46 ` Duncan
2016-05-13 8:22 ` Marc Joliet
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=58549996.M9MX6vESn9@archlinux \
--to=diegocg@gmail.com \
--cc=Nikolaus@rath.org \
--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).