All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kenny MacDermid <kenny.macdermid@gmail.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Input/Output errors
Date: Wed, 24 Feb 2016 14:02:52 -0400	[thread overview]
Message-ID: <20160224180251.GA5697@gmail.com> (raw)
In-Reply-To: <CAJCQCtQLY-zcz1e8zqNrekEfo1yo9DcDfwR_m4Y8AGaKxV32qg@mail.gmail.com>

On Tue, Feb 23, 2016 at 09:37:03PM -0700, Chris Murphy wrote:
> 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.

Thanks Chris,

The disk is a SAMSUNG MZMTE512HMHP-000L1 running f/w: EXT42L0Q. I didn't
find any updates in my searches.

I did drop the discard option, and the inode_cache and space_cache ones
as well. I'm not sure I originally got them from.

Even if it's a disk firmware bug, doesn't it seem like some layer should
report something about it? Is there any extra logging I should enable in
case it happens again?

As I don't have a way to reliable reproduce the error, I'll have to wait
and see if this helps.

  parent reply	other threads:[~2016-02-24 18:03 UTC|newest]

Thread overview: 12+ 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ó
2016-02-24 18:13         ` Kenny MacDermid
2016-02-24 18:02       ` Kenny MacDermid [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-11-01  9:18 input/output errors Dmitry Skorinko
2004-11-01 12:50 ` Thomas Gleixner
2001-06-15 11:51 Input/Output Errors qwerty t
2001-06-19  2:50 ` Stephen Herzog
2001-06-20  6:19 ` Ollie Lho

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=20160224180251.GA5697@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.