From: Ric Wheeler <rwheeler@redhat.com>
To: Supratik Goswami <supratik.goswami@webyog.com>
Cc: Sabyasachi Ruj <sabyasachi.ruj@webyog.com>,
xfs@oss.sgi.com, Vivek Goel <vivek.goel@webyog.com>,
Shrinath M <shrinath.m@webyog.com>
Subject: Re: XFS filesystem on EC2 instance corrupts and shuts down
Date: Wed, 06 Mar 2013 09:25:54 -0500 [thread overview]
Message-ID: <513751F2.2060109@redhat.com> (raw)
In-Reply-To: <CAOurMUeasru6ekDYcvVR1QnaWVJFV+-coZsUG5SgG6LnENBvXg@mail.gmail.com>
I would suggest contacting Amazon's customer support channel (or the vendor you
paid for the Linux instance you are running).
XFS developer list is probably not the correct forum to help you debug this :)
Good luck!
Ric
On 03/06/2013 08:12 AM, Supratik Goswami wrote:
> Have we created a ticket with AWS ?
>
> It could be an EBS issue who knows, we need to confirm that first.
>
> --
> Warm Regards
>
> Supratik
>
>
> On Wed, Mar 6, 2013 at 6:38 PM, Ric Wheeler <rwheeler@redhat.com
> <mailto:rwheeler@redhat.com>> wrote:
>
> On 03/06/2013 08:03 AM, Shrinath M wrote:
>
>
> On Wed, Mar 6, 2013 at 6:29 PM, Ric Wheeler <rwheeler@redhat.com
> <mailto:rwheeler@redhat.com> <mailto:rwheeler@redhat.com
> <mailto:rwheeler@redhat.com>>> wrote:
>
> 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?
>
>
> No IO errors in /var/log/messages.
> Where else should I be looking?
>
>
>
> Feb 12 19:47:18 ip-100-0-100-1 kernel: [2541168.023638] XFS (md0): I/O
> Error Detected. Shutting down filesystem
>
> Is an IO error from MD.
>
> I would suggest trying to reproduce without MD in the picture first -
> always best to try to reproduce with the simplest setup first and work
> your way up the complexity ladder,
>
> Ric
>
>
>
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-03-06 14:26 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
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 [this message]
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=513751F2.2060109@redhat.com \
--to=rwheeler@redhat.com \
--cc=sabyasachi.ruj@webyog.com \
--cc=shrinath.m@webyog.com \
--cc=supratik.goswami@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox