Re: storage, libaio, or XFS problem? 3.4.26

From: stan hoeppner <stan@hardwarefreak.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: storage, libaio, or XFS problem?  3.4.26
Date: Tue, 02 Sep 2014 12:15:05 -0500	[thread overview]
Message-ID: <5405FB19.2020208@hardwarefreak.com> (raw)
In-Reply-To: <20140901234529.GI20518@dastard>

On 09/01/2014 06:45 PM, Dave Chinner wrote:
> On Sun, Aug 31, 2014 at 10:36:25PM -0500, stan hoeppner wrote:
>> On 08/31/2014 06:57 PM, Dave Chinner wrote:
>>> On Fri, Aug 29, 2014 at 09:55:53PM -0500, Stan Hoeppner wrote:
>>>> Have you played with bcache yet?
>>>
>>> Enough to scare me. So many ways for things to go wrong, no easy way
>>> to recover when things go wrong. And that's before I even get to
>>> performance warts, like having systems stall completely because
>>> there's tens or hundreds of GB of 4k random writes that have to be
>>> flushed to slow SATA RAID6 in the cache....
>>
>> Yikes.  I hadn't yet heard such opinions expressed.  By go wrong I
>> assume you mean the btrees or cached sector data getting broken, corrupted?
> 
> bcache is a complex filesystem hidden inside a block device. If
> bcache goes AWOL, so does the all the data on your block device.
> Need I say more?

So it's no different in that regard than the black box implementations
such as LSI's CacheCade and various SAN vendor SSD caching
implementations.  Or are you saying the bcache code complexity is so
much greater that failure is more likely that the vendor implementations?

>>> PS: can you wrap your text at 68 or 72 columns so quoted text
>>> doesn't overflow 80 columns and get randomly wrapped and messed up?
>>
>> This email should be.  Lemme see what I can do with the others.  The
>> lovely Cisco VPN client I must use kills routing to my local subnet, so
>> Icedovce can't connect to my IMAP server when the VPN is active.  The
>> test hardness app requires a shell unfortunately so I have to keep the
>> tunnel open all the time, as the test runs are 40+ hours each.  My last
>> test just crashed a bit ago so I can use Icedove for this reply.
> 
> screen is your friend when it comes to keeping remote shells
> active as the network comes and goes. VPN drops out, just bring it
> back up when you need it and reconnect to the remote screen instance
> and it's like you never left....

Thanks for this tip.  I'd heard of screen before but never used it.  I
will say the man page is a bit intimidating for such an apparently
simple tool...

Stan

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs