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 20:07:11 +0200 [thread overview]
Message-ID: <20170404200711.088a3c58@harpe.intellique.com> (raw)
In-Reply-To: <889a3521-9f9d-59fd-8592-06ba40869e8f@sandeen.net>
[-- Attachment #1: Type: text/plain, Size: 1709 bytes --]
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...
> >>>
> >>> 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...
>
> So it crashed on every access, and repair fixed it, but repair said
> "nothing special" in the process? :(
>
It crashes, it reboots without complaining, so there aren't any grave
obvious upfront problems at least...
Well we'll see if it crashes again with a 4.4.59... Just in case we
removed the filestreams option in the fstab.
--
------------------------------------------------------------------------
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 --]
next prev parent reply other threads:[~2017-04-04 18:07 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 [this message]
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=20170404200711.088a3c58@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 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.