From: Sandeep Patel <spatel@omnifone.com>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: RE: XFS corruptions
Date: Mon, 11 Jan 2016 14:20:12 +0000 [thread overview]
Message-ID: <558408F298C8CE4C89D93BD56AB474E801861CBD2B@EXBE1IS02.omnifone.com> (raw)
In-Reply-To: <20151210164640.78a13865@harpe.intellique.com>
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.
Thanks
Sandeep
-----Original Message-----
From: Emmanuel Florac [mailto:eflorac@intellique.com]
Sent: 10 December 2015 15:47
To: Sandeep Patel
Cc: xfs@oss.sgi.com
Subject: Re: XFS corruptions
Le Thu, 10 Dec 2015 15:07:32 +0000
Sandeep Patel <spatel@omnifone.com> écrivait:
> Any luck with the testing. I am attaching a copy of my dmesg output
> which keeps on repeating. In this case, the error seems to be with one
> dinode.
>
I've run some tests on a 18x6 TB array, and no error occurred. However I'm running a much newer kernel, 3.18.24.
Could you maybe try installing a different kernel on some machines and see if it performs differently?
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com ______________________________________________________________________
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-01-11 14:20 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 [this message]
2016-01-11 15:16 ` Emmanuel Florac
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=558408F298C8CE4C89D93BD56AB474E801861CBD2B@EXBE1IS02.omnifone.com \
--to=spatel@omnifone.com \
--cc=eflorac@intellique.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.