All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Emmanuel Florac <eflorac@intellique.com>, linux-xfs@vger.kernel.org
Subject: Re: "interesting" crash : 3.18.44, huge xfs, nfs
Date: Tue, 4 Apr 2017 12:36:57 -0500	[thread overview]
Message-ID: <95e14081-0f1c-7458-cca2-1f33d6662037@sandeen.net> (raw)
In-Reply-To: <20170404192411.650fb403@harpe.intellique.com>


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

On 4/4/17 12:24 PM, Emmanuel Florac wrote:
> Le Tue, 4 Apr 2017 15:02:02 +0200
> Emmanuel Florac <eflorac@intellique.com> écrivait:
> 
>> Hi, 
>> here is an interesting crash dump. I've never seen this function
>> called before : "Fixing recursive fault but reboot is needed!"
>>
>> The system is frozen and must be hard rebooted. The filesystem is
>> humongous: about 400 TB.
>> Running is plain vanilla 3.18.44 (should upgrade...). I wonder if the
>> bug is still present though? 
>>
>> Context: this is a file server. There was a power failure yesterday,
>> so there's probably some corruption hidden somewhere triggering the
>> crash.

and using filestreams, apparently?

> 
> The machine goes on crashing on disk access... xfs_repair 4.9 is
> running now, and after that we'll reboot with a current kernel
> (4.4.59). Any advice?

Yep, go back in time & get an xfs_metadump before you repair it.  :(

Please do at least capture repair output.

-Eric

> The latest crash trace was still xfs related apparently:



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

  reply	other threads:[~2017-04-04 17:37 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 [this message]
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

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=95e14081-0f1c-7458-cca2-1f33d6662037@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.