public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel Florac <eflorac@intellique.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: linux-xfs@vger.kernel.org
Subject: Re: "interesting" crash : 3.18.44, huge xfs, nfs
Date: Tue, 4 Apr 2017 19:43:40 +0200	[thread overview]
Message-ID: <20170404194340.4733ccb7@harpe.intellique.com> (raw)
In-Reply-To: <95e14081-0f1c-7458-cca2-1f33d6662037@sandeen.net>

[-- Attachment #1: Type: text/plain, Size: 1276 bytes --]

Le Tue, 4 Apr 2017 12:36:57 -0500
Eric Sandeen <sandeen@sandeen.net> écrivait:

> >> 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?

I don't see why or where we'd use filestreams there... What's the use
case actually?
 
> > 
> > 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.  :(

You know how it goes it crashes, users scream, administrator jumps on
xfs_repair, and the rest is history.
 
> Please do at least capture repair output.
> 

Well the only thing I know is "there was nothing special in xfs_repair
output"... I'll tell the admin to catch the output next time if
necessary...


-- 
------------------------------------------------------------------------
Emmanuel Florac     |   Direction technique
                    |   Intellique
                    |	<eflorac@intellique.com>
                    |   +33 1 78 94 84 02
------------------------------------------------------------------------

[-- Attachment #2: Signature digitale OpenPGP --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2017-04-04 17:43 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 [this message]
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=20170404194340.4733ccb7@harpe.intellique.com \
    --to=eflorac@intellique.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox