From: Eric Sandeen <sandeen@sandeen.net>
To: Dave Chinner <david@fromorbit.com>
Cc: blacknred <leo1783@hotmail.co.uk>, xfs@oss.sgi.com
Subject: Re: possible xfs corruption
Date: Wed, 08 Dec 2010 21:44:14 -0600 [thread overview]
Message-ID: <4D00508E.5040408@sandeen.net> (raw)
In-Reply-To: <20101207221009.GA29333@dastard>
On 12/7/10 4:10 PM, Dave Chinner wrote:
> On Tue, Dec 07, 2010 at 03:49:49AM -0800, blacknred wrote:
>>
>> Hi...
>>
>> I'm stuck with a storage issue on reboot. Initially doubted the storage, but
>> dmesg throws these errors. Now wondering whether this is a fs issue? Any
>> thoughts as to whats going on here?
>>
>>
>> XFS: failed to locate log tail
>> XFS: log mount/recovery failed: error 117
>> XFS: log mount failed
>> XFS mounting filesystem cciss/c0d0
>> Filesystem "cciss/c0d0": XFS internal error xlog_clear_stale_blocks(2) at
>> line 1237 of file
>
> Which indicates that the head and/or the tail of the log are not
> valid. Can you provide the output of:
>
> # xfs_logprint -d /dev/cciss/c0d0
>
> So we can see what the head/tail values are in the log?
>
>> /home/buildsvn/rpmbuild/BUILD/xfs-kmod-0.4/_kmod_build_PAE/xfs_log_recover.c.
>
> CentOS kernel? How old?
Assuning it's centos5, there's really no need to be using an xfs kmod there
anymore, the module shipped with the kernel in recent versions of the OS
is really the one you want to use. That kmod is ancient and unmaintained.
Although I suspect the storage is more likely at fault here. :)
-Eric
> Cheers,
>
> Dave.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-12-09 3:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 11:49 possible xfs corruption blacknred
2010-12-07 14:10 ` Emmanuel Florac
2010-12-07 15:11 ` blacknred
2010-12-07 15:42 ` Emmanuel Florac
2010-12-07 17:30 ` blacknred
2010-12-07 18:15 ` Stan Hoeppner
2010-12-07 19:32 ` Michael Monnerie
2010-12-07 22:10 ` Dave Chinner
2010-12-09 3:44 ` Eric Sandeen [this message]
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=4D00508E.5040408@sandeen.net \
--to=sandeen@sandeen.net \
--cc=david@fromorbit.com \
--cc=leo1783@hotmail.co.uk \
--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