All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ric Wheeler <rwheeler@redhat.com>
To: Shrinath M <shrinath.m@webyog.com>
Cc: Sabyasachi Ruj <sabyasachi.ruj@webyog.com>,
	Vivek Goel <vivek.goel@webyog.com>,
	xfs@oss.sgi.com
Subject: Re: XFS filesystem on EC2 instance corrupts and shuts down
Date: Wed, 06 Mar 2013 07:59:36 -0500	[thread overview]
Message-ID: <51373DB8.2020707@redhat.com> (raw)
In-Reply-To: <CAOdS1h=7X4O1O7X8YOwxtLm7G=fc+J+6hJxJ1RKbDmfTZXTpeg@mail.gmail.com>

On 03/06/2013 03:07 AM, Shrinath M wrote:
> We are experiencing a strange XFS corruption issue. If we look in 
> /var/log/messages, it simply says -
>
>     Mar  5 01:14:33 ip-100-0-100-1 kernel: [14139930.248619] XFS (md0): 
> Corruption detected. Unmount and run xfs_repair
>
> It shuts down the filesystem after this. On rebooting, it calls xfs_repair 
> automatically and everything comes back to normal.
> We have had 2 such occurrences till now, I am attaching the relevant parts of 
> /var/log/messages here, assuming someone can enlighten me on whats going wrong.
>
> Machine details are as follows -
>
> We are using Amazon AMI version: Amazon Linux AMI release 2012.09 We are 
> running 8 EBS volumes of 512 MB each, in RAID 0 Array. $~: uname -a Linux 
> ip-100-0-100-1 3.2.34-55.46.amzn1.x86_64 #1 SMP Tue Nov 20 10:06:15 UTC 2012 
> x86_64 x86_64 x86_64 GNU/Linux
>
>
> Ask me if anyone wants any more details
>

I think that you would need to verify that the Amazon storage is not throwing 
errors - do your logs show IO errors or issues before XFS hits an issue?

Thanks!

Ric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2013-03-06 12:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-06  8:07 XFS filesystem on EC2 instance corrupts and shuts down Shrinath M
2013-03-06 12:59 ` Ric Wheeler [this message]
2013-03-06 13:03   ` Shrinath M
2013-03-06 13:08     ` Ric Wheeler
2013-03-06 13:12       ` Supratik Goswami
2013-03-06 13:15         ` Supratik Goswami
2013-03-06 14:25         ` Ric Wheeler
2013-03-13 18:07           ` Shrinath M
2013-03-13 18:24             ` Ben Myers
2013-03-13 18:56             ` Eric Sandeen
2013-03-13 19:10               ` Eric Sandeen
2013-03-13 23:42               ` Dave Chinner
2013-03-14  1:28                 ` Shrinath M
2013-03-14 13:31                   ` Stan Hoeppner
2013-03-14 22: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=51373DB8.2020707@redhat.com \
    --to=rwheeler@redhat.com \
    --cc=sabyasachi.ruj@webyog.com \
    --cc=shrinath.m@webyog.com \
    --cc=vivek.goel@webyog.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.