2016-05-12 19:41 keltezéssel, Nikolaus Rath írta:
On May 12 2016, Diego Calleja <dieg...@gmail.com> wrote:
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
Thanks for the pointer. So according to these reports, the IO errors
happen with:
1. dm-crypt, LVM and mount options
rw,noatime,compress=lzo,ssd,discard,space_cache,autodefrag,inode_cache
2. dm-crypt, no LVM, and mount options
noatime,compress,nossd
I can add the following data point:
3. dm-crypt on LVM, and mount options
relatime,compress=lzo
(Just to preserve this for the future)
I don't want to repeat my e-mails in the past, but I think I have a
similar issue. In short: xen virtual machine. The files that rarely
become unreadable (I/O error but no error in dmesg or anywhere) are
mysql MyIsam database files, and they are always small. Like 16kbyte for
example, or smaller. Sometimes dropping the fs cache fixes the problem,
sometimes not. Umount / mount always fixes the problem. Scrub says the
filesystem is OK (when the file is unreadable).
I experienced similar problem with log files (smtp or apache log files),
but it is rare. It happens 1-2 times in a month on a heavy loaded
mail/web server. (the log file io error is not a real problem for me,
mysql is.). The problem present from 3.18 to 4.5.
I started to migrate mysql table files to innodb, but i think this is
only a workaround.
László Szalma
Best,
-Nikolaus
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
