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, 30 Nov 2015 18:06:55 +0000 [thread overview]
Message-ID: <558408F298C8CE4C89D93BD56AB474E8018617B3A6@EXBE1IS02.omnifone.com> (raw)
In-Reply-To: <20151130184048.3fa123e0@harpe.intellique.com>
Hi Emmanuel,
Thanks for the response.
[root@gc003b ~]# xfs_info /dev/sdb
meta-data=/dev/sdb isize=512 agcount=52, agsize=268435455 blks
= sectsz=4096 attr=2, projid32bit=1
= crc=0
data = bsize=4096 blocks=13916176384, imaxpct=1
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0
log =internal bsize=4096 blocks=521728, version=2
= sectsz=4096 sunit=1 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
We have 18 nodes each with 2 of these arrays and we are seeing this across the board.
I have updated the xfsprogs to 3.1.11-1.0.6.el6.x86_64 which is the latest version available on our yum repo.
This is a production system so upgrading to the latest version is not very easy.
Thanks
Sandeep
-----Original Message-----
From: Emmanuel Florac [mailto:eflorac@intellique.com]
Sent: 30 November 2015 17:41
To: Sandeep Patel
Cc: xfs@oss.sgi.com
Subject: Re: XFS corruptions
Le Mon, 30 Nov 2015 16:51:57 +0000
Sandeep Patel <spatel@omnifone.com> écrivait:
>
> What could be causing these issues?
>
> Thanks for your help in advanced.
Hard to say, what does xfs_info /mountpoint says?
Are the corruption occuring on all machines or do they target some systems more?
Did you try repairing using the latest (4.2 or 4.3) version of xfs_repair? The Oracle Linux version is probably seriously out of date.
--
------------------------------------------------------------------------
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:[~2015-11-30 18:07 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 [this message]
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
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=558408F298C8CE4C89D93BD56AB474E8018617B3A6@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.