From: "Paul B. Henson" <henson@acm.org>
To: "'David H. Rhodes Clymer'" <david@zettazebra.com>
Cc: linux-bcache@vger.kernel.org
Subject: RE: Another bcache hang
Date: Fri, 22 Nov 2013 11:46:56 -0800 [thread overview]
Message-ID: <155b01cee7bb$9befd5d0$d3cf8170$@acm.org> (raw)
In-Reply-To: <20131122034919.GA25040@professorx.home.zettazebra.com>
> From: David H. Rhodes Clymer [mailto:david@zettazebra.com]
> Sent: Thursday, November 21, 2013 7:49 PM
>
> Laziness, mostly. The RAID1 array is a PV that houses filesystems we'd
> rather thot lose. The development databases are not so critical - we
> rebuild them at least once a week anyway. The use of LVs was a quick
> and easy way to test various caching implementations without increasing
> the risk of data loss or corruption in the rest of the system.
Ah, okay, I get it; you had a pre-existing PV with production stuff on it
you didn't want to lose and were just testing out bcache, makes sense.
I haven't seen any responses to your hang report though :(, while obviously
there's no expectation of support, it's always nice if you're going to drop
something into production to have a forum where the experts give you a hand
when things blow chunks.
prev parent reply other threads:[~2013-11-22 19:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 13:56 Another bcache hang David H. Rhodes Clymer
2013-11-22 1:07 ` Paul B. Henson
2013-11-22 3:49 ` David H. Rhodes Clymer
2013-11-22 14:35 ` Jason Warr
2013-11-22 19:51 ` Paul B. Henson
2013-11-22 20:34 ` Jason Warr
2013-11-22 23:52 ` Paul B. Henson
2013-11-23 0:38 ` Matthew Patton
2013-11-23 0:43 ` Paul B. Henson
2013-11-23 1:02 ` Jason Warr
2013-11-23 2:14 ` Paul B. Henson
2013-11-23 2:38 ` Jason Warr
2013-11-22 19:46 ` Paul B. Henson [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='155b01cee7bb$9befd5d0$d3cf8170$@acm.org' \
--to=henson@acm.org \
--cc=david@zettazebra.com \
--cc=linux-bcache@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.