From: Rolf Fokkens <rolf@rolffokkens.nl>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>,
"linux-bcache@vger.kernel.org" <linux-bcache@vger.kernel.org>
Cc: Kent Overstreet <kmo@daterainc.com>
Subject: Re: bcache fails after reboot if discard is enabled
Date: Sat, 03 Jan 2015 17:32:32 +0100 [thread overview]
Message-ID: <54A819A0.9010501@rolffokkens.nl> (raw)
In-Reply-To: <54A66C44.6070505@profihost.ag>
I've been using discard for a while, but I ran a few times in serious FS
corruptions. After disabling discard bcache was stable again.
So far I tributed the corruptions to a low-cost SSD which probably
didn't handle discard very well. But this was only an assumptions.
I didn't experience specific reboot problems like you describe.
On 01/02/2015 11:00 AM, Stefan Priebe - Profihost AG wrote:
> I'm sorry the backtraces were incomplete.
>
> Am 02.01.2015 um 10:47 schrieb Stefan Priebe - Profihost AG:
>> Hi,
>>
>> while running 3.10 or 3.18 kernel i've problems enabling discard.
>> Strangely this only appears on reboot or crash. While these situations
>> work fine without discard.
>>
>> bcache completely fails when discard is enabled for reboot or crash.
>> Strangely it works fine while "running".
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-01-03 16:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-02 9:47 bcache fails after reboot if discard is enabled Stefan Priebe - Profihost AG
2015-01-02 10:00 ` Stefan Priebe - Profihost AG
2015-01-03 16:32 ` Rolf Fokkens [this message]
2015-01-03 19:32 ` Stefan Priebe
2015-01-05 0:06 ` Michael Goertz
2015-02-09 19:46 ` Kai Krakow
2015-04-08 0:06 ` Dan Merillat
2015-04-08 18:17 ` Eric Wheeler
2015-04-08 18:27 ` Stefan Priebe
2015-04-08 19:31 ` Eric Wheeler
2015-04-08 19:54 ` Kai Krakow
2015-04-08 22:02 ` Dan Merillat
2015-04-10 23:00 ` Kai Krakow
2015-04-11 0:14 ` Kai Krakow
2015-04-11 6:31 ` Dan Merillat
2015-04-11 6:54 ` Dan Merillat
2015-04-11 7:52 ` Kai Krakow
2015-04-11 18:53 ` Dan Merillat
[not found] ` <CAPL5yKfpk8+6Vw cUVcwJ9QxAZJQmqaa98spCyT7+LekkRvkeAw@mail.gmail.com>
2015-04-11 20:09 ` Kai Krakow
2015-04-12 5:56 ` Dan Merillat
2015-04-29 17:48 ` Dan Merillat
2015-04-29 18:00 ` Ming Lin
2015-04-29 19:57 ` Kai Krakow
2015-04-08 18:46 ` Kai Krakow
2015-06-05 5:11 ` Kai Krakow
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=54A819A0.9010501@rolffokkens.nl \
--to=rolf@rolffokkens.nl \
--cc=kmo@daterainc.com \
--cc=linux-bcache@vger.kernel.org \
--cc=s.priebe@profihost.ag \
/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.