linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Szalma László" <dblaci@dblaci.hu>
To: linux-btrfs@vger.kernel.org
Subject: Re: Input/Output errors
Date: Wed, 24 Feb 2016 09:58:08 +0100	[thread overview]
Message-ID: <56CD70A0.30201@dblaci.hu> (raw)
In-Reply-To: <CAJCQCtQLY-zcz1e8zqNrekEfo1yo9DcDfwR_m4Y8AGaKxV32qg@mail.gmail.com>

2016-02-24 05:37 keltezéssel, Chris Murphy írta:
> On Tue, Feb 23, 2016 at 8:02 PM, Kenny MacDermid
> <kenny.macdermid@gmail.com> wrote:
>
>> rw,noatime,compress=lzo,ssd,discard,space_cache,autodefrag,inode_cache
> It sounds like an ssd trim bug. I'd check the firmware for updates. If
> it's up to date, I'd drop discard mount option first and try to
> reproduce. Or just use the default mount options and try to reproduce,
> then add them back one at a time until you discover the culprit.
>
> Also, how many files/directories are there? inode_cache isn't
> recommended for most use cases. And space_cache is the default so it
> doesn't need to be listed.
>
>
>

As i wrote to the list a few weeks ago, this problem seems to be the 
same I have.

The difference:

- i use mount options: noatime,compress,nossd
- I don't use dm-crypt, but these machines are Xen pvms (there is a 
virtualization layer between btrfs and lvm)

The same:

- io error without any error or message in the dmesg.
- umount / mount always fixes the problem (for some time)

More info:

- these files are usually smalls (mysql myisam files, 10-20-50 kbyte 
size, without heave fragmentation)
- defrag don't help
- scrub always works (no errors) but not fix the errors
- no hw or hw read error on the block device (in any layer)
- get this problem with 4.4.1 kernel too (seems to be somewhat less 
frequent than before, but the problem happened with 3.18 and on)
- echo 3 > /proc/sys/vm/drop_caches    sometimes fixes the problem, but 
not every time
- the problem is happening rarely, sometimes there are days without error
- the problem is not for specific hardware or virtual machine

I can try any debug option or patch if needed.

László Szalma

  reply	other threads:[~2016-02-24  9:07 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
2016-02-24  3:02   ` Kenny MacDermid
2016-02-24  4:37     ` Chris Murphy
2016-02-24  8:58       ` Szalma László [this message]
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=56CD70A0.30201@dblaci.hu \
    --to=dblaci@dblaci.hu \
    --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).