From: Slava Pestov <sp@datera.io>
To: "Stephen R. van den Berg" <srb@cuci.nl>
Cc: Kent Overstreet <kmo@daterainc.com>,
"linux-bcache@vger.kernel.org" <linux-bcache@vger.kernel.org>
Subject: Re: 3.18.3 + latest bcache-dev
Date: Wed, 21 Jan 2015 14:47:16 -0800 [thread overview]
Message-ID: <CACHGV4J3Ler_+RHcd6x0nEfSKTnWQLqhrze97XzcFe-30+xu6A@mail.gmail.com> (raw)
In-Reply-To: <20150121110400.GA14729@cuci.nl>
On Wed, Jan 21, 2015 at 3:04 AM, Stephen R. van den Berg <srb@cuci.nl> wrote:
> Jan 21 11:21:40 ip144 kernel: ata11.00: exception Emask 0x0 SAct 0x7fffffff SErr 0x0 action 0x0
> Jan 21 11:21:40 ip144 kernel: ata11.00: irq_stat 0x40000008
> Jan 21 11:21:40 ip144 kernel: ata11.00: failed command: READ FPDMA QUEUED
> Jan 21 11:21:40 ip144 kernel: ata11.00: cmd 60/00:c0:10:d0:d9/04:00:01:00:00/40 tag 24 ncq 524288 in
> Jan 21 11:21:40 ip144 kernel: res 41/40:00:d0:d1:d9/00:00:01:00:00/00 Emask 0x409 (media error) <F>
> Jan 21 11:21:40 ip144 kernel: ata11.00: status: { DRDY ERR }
> Jan 21 11:21:40 ip144 kernel: ata11.00: error: { UNC }
> Jan 21 11:21:40 ip144 kernel: ata11.00: configured for UDMA/133
>
I'm not sure this is related. Do you see it during normal operation
ever? It is possible that we're spinning in softirq context or
something, starving the device, but I'm not sure...
> Jan 21 11:43:46 ip144 kernel: bcache: register_cache() registered cache device sda3
> Jan 21 11:43:46 ip144 kernel: bcache: register_cache() registered cache device sdb3
> Jan 21 11:43:46 ip144 kernel: bcache: register_bdev() registered backing device sdg
> Jan 21 11:43:46 ip144 kernel: bcache: register_bdev() registered backing device sdc
> Jan 21 11:43:46 ip144 kernel: bcache: register_bdev() registered backing device sdf
> Jan 21 11:43:46 ip144 kernel: bcache: register_bdev() registered backing device sde
> Jan 21 11:43:46 ip144 kernel: bcache: register_bdev() registered backing device sdd
> Jan 21 11:43:46 ip144 kernel: bcache: error on 04063132-f7e1-4f29-a3aa-675491b426f4: sdb3: bad magic (got 17495323148306469098 expect 5629218783827753365) while reading prios from bucket 16868
> Jan 21 11:43:46 ip144 kernel: bcache: register_bcache() error opening /dev/sdb3: error reading priorities
This is a bcache-dev bug that we just hit in our automation runs after
adding some more reboot tests. We're working on it.
Slava
next prev parent reply other threads:[~2015-01-21 22:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 1:24 3.18.3 + latest bcache-dev Stephen R. van den Berg
2015-01-21 8:00 ` Kent Overstreet
2015-01-21 11:04 ` Stephen R. van den Berg
2015-01-21 16:45 ` Stephen R. van den Berg
2015-01-22 12:33 ` patch (Re: 3.18.3 + latest bcache-dev) Stephen R. van den Berg
2015-01-22 12:56 ` Stephen R. van den Berg
2015-01-21 22:47 ` Slava Pestov [this message]
2015-01-21 23:04 ` 3.18.3 + latest bcache-dev Stephen R. van den Berg
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=CACHGV4J3Ler_+RHcd6x0nEfSKTnWQLqhrze97XzcFe-30+xu6A@mail.gmail.com \
--to=sp@datera.io \
--cc=kmo@daterainc.com \
--cc=linux-bcache@vger.kernel.org \
--cc=srb@cuci.nl \
/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.