From: Kent Overstreet <koverstreet-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
To: Pierre Beck <debian-bugs-MZZvbRqs/9F0RdzJJlgK+g@public.gmane.org>
Cc: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Loosing transactions
Date: Wed, 30 Jan 2013 12:18:17 -0800 [thread overview]
Message-ID: <20130130201817.GA12631@moria.home.lan> (raw)
In-Reply-To: <51097D0A.6040204-MZZvbRqs/9F0RdzJJlgK+g@public.gmane.org>
On Wed, Jan 30, 2013 at 09:05:31PM +0100, Pierre Beck wrote:
> Am 30.01.2013 20:02, schrieb Kent Overstreet:
> >That delay is a parameter - /sys/fs/bcache/<cache set>/journal_delay_ms.
> >Can you set it to 0 and see what happens? It might reduce the number of
> >missing transactions, eliminate the missing transactions... or have no
> >effect at all.
> >
>
> Test passed. Double-checked. No transactions lost.
None at all, ever?
That's actually kind of annoying, because we can't definitively
distinguish between "fixes bug completely" and "makes bug a lot harder
to actually detect". Bah :p
Can you run blktrace on the bcache device and the SSD for a second or
two while your msql test is running? Maybe if I stare at the trace I'll
get lucky and see something wrong.
> I really want to see bcache in mainline kernel soon. It's such a
> great addition for storage arrays. Let's polish it up. When you have
> a fix, I'll test a full storage stack on it. Ext4 alone is boring
> :-)
Working on it :D
prev parent reply other threads:[~2013-01-30 20:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 20:14 Loosing transactions Pierre Beck
[not found] ` <51004490.704-MZZvbRqs/9F0RdzJJlgK+g@public.gmane.org>
2013-01-24 23:35 ` Kent Overstreet
[not found] ` <20130124233559.GO26407-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2013-01-28 14:45 ` Pierre Beck
[not found] ` <51068F01.9060000-MZZvbRqs/9F0RdzJJlgK+g@public.gmane.org>
2013-01-29 19:01 ` Kent Overstreet
[not found] ` <20130129190133.GL26407-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2013-01-29 19:09 ` Kent Overstreet
[not found] ` <20130129190942.GM26407-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2013-01-29 20:16 ` Pierre Beck
[not found] ` <51082E02.7000908-MZZvbRqs/9F0RdzJJlgK+g@public.gmane.org>
2013-01-30 19:02 ` Kent Overstreet
[not found] ` <20130130190220.GS26407-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2013-01-30 20:05 ` Pierre Beck
[not found] ` <51097D0A.6040204-MZZvbRqs/9F0RdzJJlgK+g@public.gmane.org>
2013-01-30 20:18 ` Kent Overstreet [this message]
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=20130130201817.GA12631@moria.home.lan \
--to=koverstreet-hpiqsd4aklfqt0dzr+alfa@public.gmane.org \
--cc=debian-bugs-MZZvbRqs/9F0RdzJJlgK+g@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.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