All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Shrinath M <shrinath.m@webyog.com>
Cc: Sabyasachi Ruj <sabyasachi.ruj@webyog.com>,
	xfs@oss.sgi.com, Supratik Goswami <supratik.goswami@webyog.com>,
	Ric Wheeler <rwheeler@redhat.com>,
	Vivek Goel <vivek.goel@webyog.com>
Subject: Re: XFS filesystem on EC2 instance corrupts and shuts down
Date: Wed, 13 Mar 2013 14:10:58 -0500	[thread overview]
Message-ID: <5140CF42.6000206@sandeen.net> (raw)
In-Reply-To: <5140CBE3.80705@sandeen.net>

On 3/13/13 1:56 PM, Eric Sandeen wrote:

> It's a little odd that you get:
> 
> Feb 12 19:47:18 ip-100-0-100-1 kernel: [2541168.014259] XFS (md0): xfs_iunlink_remove: xfs_itobp() returned error 117.
> 
> because AFAIK, 117 is not any known error number (not even xfs's old EFSCORRUPTED value, which was 990)
> But I see other references in various places to this error number coming from XFS - so I'm not sure.

Ugh, no it's not odd, it's:

#define EUCLEAN 117
which maps to EFSCORRUPTED.  Sorry for that noise, how'd I miss that?  :(

Anyway, turn up the error level & see if you get more info.

-Eric

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

  reply	other threads:[~2013-03-13 19:11 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
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 [this message]
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=5140CF42.6000206@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=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 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.