All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: "interesting" crash : 3.18.44, huge xfs, nfs
Date: Tue, 4 Apr 2017 13:16:48 -0500	[thread overview]
Message-ID: <5ae8a2ae-c62a-d8fd-268c-4e5d90e331d6@sandeen.net> (raw)
In-Reply-To: <20170404200711.088a3c58@harpe.intellique.com>


[-- Attachment #1.1: Type: text/plain, Size: 607 bytes --]

On 4/4/17 1:07 PM, Emmanuel Florac wrote:
> Le Tue, 4 Apr 2017 12:45:07 -0500
> Eric Sandeen <sandeen@sandeen.net> écrivait:
> 
>>>
>>> I don't see why or where we'd use filestreams there... What's the
>>> use case actually?  
>>
>> well, it's in your crash backtrace, so you tell me ;)
>>
> 
> I remember now... There writing files in long sequences, so that's what
> the filestream option is for. It worked fine for a few months though...

I'm not saying it's the root cause, or wrong, but it is an interesting
datapoint for the server config.  It's not a heavily used option.

-Eric


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 867 bytes --]

      reply	other threads:[~2017-04-04 18:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-04 13:02 "interesting" crash : 3.18.44, huge xfs, nfs Emmanuel Florac
2017-04-04 17:24 ` Emmanuel Florac
2017-04-04 17:36   ` Eric Sandeen
2017-04-04 17:43     ` Emmanuel Florac
2017-04-04 17:45       ` Eric Sandeen
2017-04-04 18:07         ` Emmanuel Florac
2017-04-04 18:16           ` Eric Sandeen [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=5ae8a2ae-c62a-d8fd-268c-4e5d90e331d6@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=eflorac@intellique.com \
    --cc=linux-xfs@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.