From: Emmanuel Florac <eflorac@intellique.com>
To: Sandeep Patel <spatel@omnifone.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: XFS corruptions
Date: Mon, 11 Jan 2016 16:16:02 +0100 [thread overview]
Message-ID: <20160111161602.0c8413ca@harpe.intellique.com> (raw)
In-Reply-To: <558408F298C8CE4C89D93BD56AB474E801861CBD2B@EXBE1IS02.omnifone.com>
Le Mon, 11 Jan 2016 14:20:12 +0000
Sandeep Patel <spatel@omnifone.com> écrivait:
> Hi Emmanuel,
>
> I have managed to upgrade our kernel to 3.8.13-118.2.2.el6uek.x86_64
> which was the latest available on our repo. I will let you know how I
> get on.
>
OK. I'm pretty confident it should enhance the situation :)
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-01-11 15:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 16:51 XFS corruptions Sandeep Patel
2015-11-30 17:40 ` Emmanuel Florac
2015-11-30 18:06 ` Sandeep Patel
2015-11-30 18:45 ` Emmanuel Florac
2015-12-01 12:18 ` Sandeep Patel
2015-12-01 13:50 ` Emmanuel Florac
2015-12-01 14:01 ` Sandeep Patel
2015-12-10 15:07 ` Sandeep Patel
2015-12-10 15:46 ` Emmanuel Florac
2015-12-10 19:51 ` Sandeep Patel
2016-01-11 14:20 ` Sandeep Patel
2016-01-11 15:16 ` Emmanuel Florac [this message]
2016-03-16 13:15 ` Sandeep Patel
2016-03-16 14:07 ` Emmanuel Florac
2015-11-30 21:51 ` Dave Chinner
2015-11-30 22:04 ` Darrick J. Wong
2015-12-10 16:46 ` Eric Sandeen
-- strict thread matches above, loose matches on Subject: below --
2008-09-04 17:11 xfs corruptions Bernd Schubert
2008-09-04 23:02 ` Dave Chinner
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=20160111161602.0c8413ca@harpe.intellique.com \
--to=eflorac@intellique.com \
--cc=spatel@omnifone.com \
--cc=xfs@oss.sgi.com \
/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.