From: Eric Sandeen <sandeen@sandeen.net>
To: Gregory Farnum <gregory.farnum@dreamhost.com>
Cc: xfs@oss.sgi.com
Subject: Re: EFSCORRUPTED on mount?
Date: Tue, 22 Nov 2011 12:52:51 -0600 [thread overview]
Message-ID: <4ECBEF83.5020607@sandeen.net> (raw)
In-Reply-To: <CAF3hT9Cu+56WJqzHVu+fMgquddwoMsfW-WC8CvRRBtC4PA3uHw@mail.gmail.com>
On 11/22/11 12:47 PM, Gregory Farnum wrote:
> On Tue, Nov 22, 2011 at 7:06 AM, Eric Sandeen <sandeen@sandeen.net> wrote:
>> > Others have had good comments but also:
>> >
>>> >> 2011-11-17 16:00:37.294876 7f83f3eef720 filestore(/mnt/osd.17)
>>> >> truncate meta/pginfo_12.7c8/0 size 0
>>> >> 2011-11-17 16:00:37.483407 7f83f3eef720 filestore(/mnt/osd.17)
>>> >> truncate meta/pginfo_12.7c8/0 size 0 = -117
>>> >> 2011-11-17 16:00:37.483476 7f83f3eef720 filestore(/mnt/osd.17) error
>>> >> error 117: Structure needs cleaning not handled
>> >
>> > was there anything in dmesg/system logs right at this point? XFS should
>> > have said something about this original error.
> Whoops. The following is a sample of what was in dmesg and kern.log
> after that point but before I did anything else (it repeated a lot but
> there weren't any other lines of output):
> xfs/xfs_buf.c. Return address = 0xffffffff811c2aa8
> [56459.526220] XFS (sdg1): xfs_log_force: error 5 returned.
> [56489.544153] XFS (sdg1): xfs_log_force: error 5 returned.
> [56519.562087] XFS (sdg1): xfs_log_force: error 5 returned.
> [56549.580021] XFS (sdg1): xfs_log_force: error 5 returned.
> [56579.597956] XFS (sdg1): xfs_log_force: error 5 returned.
> [56609.615889] XFS (sdg1): xfs_log_force: error 5 returned.
> [56613.036430] XFS (sdg1): xfs_log_force: error 5 returned.
Ok, error 5 is EIO:
8 include/asm-generic/errno-base.h 8 #define EIO 5
So the very first error you saw was "xfs_do_force_shutdown(0x1) called from line..." ?
Or the "xfs_log_force error 5 returned?" I'm wondering if there was more
before this.
It's worth looking carefully to see the very first problem reported by xfs,
and posibly from storage before that. (i.e. did your storage go wonky?)
-Eric
> [56613.041731] XFS (sdg1): xfs_do_force_shutdown(0x1) called from line
> 1037 of file fs/xfs/xfs_buf.c. Return address = 0xffffffff811c2aa8
> [56619.430497] XFS (sdg1): xfs_log_force: error 5 returned.
> [56619.435796] XFS (sdg1): xfs_do_force_shutdown(0x1) called from line
> 1037 of file fs/xfs/xfs_buf.c. Return address = 0xffffffff811c2aa8
>
> Thanks!
> -Greg
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-11-22 18:52 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 [this message]
2011-11-22 19:29 ` Gregory Farnum
2011-11-22 21:53 ` Eric Sandeen
2011-11-22 22:55 ` Christoph Hellwig
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=4ECBEF83.5020607@sandeen.net \
--to=sandeen@sandeen.net \
--cc=gregory.farnum@dreamhost.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