From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Gregory Farnum <gregory.farnum@dreamhost.com>, xfs@oss.sgi.com
Subject: Re: EFSCORRUPTED on mount?
Date: Tue, 22 Nov 2011 17:55:37 -0500 [thread overview]
Message-ID: <20111122225537.GA25530@infradead.org> (raw)
In-Reply-To: <4ECC19C3.5070905@sandeen.net>
On Tue, Nov 22, 2011 at 03:53:07PM -0600, Eric Sandeen wrote:
> > Ending recovery (logdev: internal)
> > ...
>
> All that recovery a result of the icky shutdown procedure I guess....
>
> > Nov 17 16:01:01 cephstore6358 kernel: [ 214.214688] XFS: Internal
> > error XFS_WANT_CORRUPTED_GOTO at line 1664 of file fs/xfs/xfs_alloc.c.
> > Caller 0xffffffff811d6b71
>
> And this was the first indication of trouble.
allocation btree corruption - we try to free a block, which had already
been inserted into the by-size allocation btree. This very much looks
like a cache failure to me.
> > Nov 17 16:01:01 cephstore6358 kernel: [ 214.302172]
> > [<ffffffff810d2b11>] ? sys_truncate+0x171/0x173
> > Nov 17 16:01:01 cephstore6358 kernel: [ 214.307846]
> > [<ffffffff8166c07b>] ? system_call_fastpath+0x16/0x1b
> > Nov 17 16:01:01 cephstore6358 kernel: [ 214.314031] XFS (sdg1):
> > xfs_do_force_shutdown(0x8) called from line 3864 of file
> > fs/xfs/xfs_bmap.c. Return address = 0xffffffff811e2046
>
> by here it had shut down, and you were just riding along when
> it went kablooey. Any non-xfs error just before this point?
And this was the caller of xfs_free_extent, now shuting the fs down
because of the above error.
> > Nov 17 16:01:01 cephstore6358 kernel: [ 214.340451] XFS (sdg1):
> > Corruption of in-memory data detected. Shutting down filesystem
> > Nov 17 16:01:01 cephstore6358 kernel: [ 214.348518] XFS (sdg1):
> > Please umount the filesystem and rectify the problem(s)
> > Nov 17 16:01:01 cephstore6358 kernel: [ 227.789285] XFS (sdg1):
> > xfs_log_force: error 5 returned.
> > Nov 17 16:01:01 cephstore6358 kernel: [ 229.820255] XFS (sdg1):
> > xfs_log_force: error 5 returned.
>
> To be honest I'm not sure offhand if this error 5 (EIO) is a
> result of the shutdown, or the cause of it.
It is. One the filesystem has been shut down xfs_log_force will
always return EIO. The printk for is rather useless, though.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-11-22 22:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 18:06 EFSCORRUPTED on mount? Gregory Farnum
2011-11-21 21:52 ` Emmanuel Florac
2011-11-21 22:13 ` Ben Myers
2011-11-22 0:21 ` Gregory Farnum
2011-11-22 1:41 ` Dave Chinner
2011-11-22 18:47 ` Gregory Farnum
2011-11-22 18:52 ` Eric Sandeen
2011-11-22 19:29 ` Gregory Farnum
2011-11-22 21:53 ` Eric Sandeen
2011-11-22 22:55 ` Christoph Hellwig [this message]
2011-11-23 0:03 ` Gregory Farnum
2011-11-23 15:51 ` Christoph Hellwig
2011-11-22 22:11 ` Christoph Hellwig
2011-11-22 8:06 ` Emmanuel Florac
2011-11-22 15:06 ` Eric Sandeen
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=20111122225537.GA25530@infradead.org \
--to=hch@infradead.org \
--cc=gregory.farnum@dreamhost.com \
--cc=sandeen@sandeen.net \
--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