On Wed, 2017-07-26 at 21:08 +0800, Yan, Zheng wrote:
> On Tue, Jul 25, 2017 at 10:50 PM, Jeff Layton wrote:
> > From: Jeff Layton
> >
> > Testing ceph for proper writeback error handling turns out to be quite
> > difficult. I tried using iptables to block
On Wed, 2017-07-26 at 21:08 +0800, Yan, Zheng wrote:
> On Tue, Jul 25, 2017 at 10:50 PM, Jeff Layton wrote:
> > From: Jeff Layton
> >
> > Testing ceph for proper writeback error handling turns out to be quite
> > difficult. I tried using iptables to block traffic but that didn't
> > give
On Tue, Jul 25, 2017 at 10:50 PM, Jeff Layton wrote:
> From: Jeff Layton
>
> Testing ceph for proper writeback error handling turns out to be quite
> difficult. I tried using iptables to block traffic but that didn't
> give reliable results.
>
> I hacked
On Tue, Jul 25, 2017 at 10:50 PM, Jeff Layton wrote:
> From: Jeff Layton
>
> Testing ceph for proper writeback error handling turns out to be quite
> difficult. I tried using iptables to block traffic but that didn't
> give reliable results.
>
> I hacked in this wb_fault switch that makes the
From: Jeff Layton
Testing ceph for proper writeback error handling turns out to be quite
difficult. I tried using iptables to block traffic but that didn't
give reliable results.
I hacked in this wb_fault switch that makes the filesystem pretend that
writeback failed, even
From: Jeff Layton
Testing ceph for proper writeback error handling turns out to be quite
difficult. I tried using iptables to block traffic but that didn't
give reliable results.
I hacked in this wb_fault switch that makes the filesystem pretend that
writeback failed, even when it succeeds.
6 matches
Mail list logo