[Top] [All Lists]

Re: possible xfs corruption

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: possible xfs corruption
From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Wed, 08 Dec 2010 21:44:14 -0600
Cc: blacknred <leo1783@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
In-reply-to: <20101207221009.GA29333@dastard>
References: <30395558.post@xxxxxxxxxxxxxxx> <20101207221009.GA29333@dastard>
User-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv: Gecko/20101027 Thunderbird/3.1.6
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.  :)


> Cheers,
> Dave.

<Prev in Thread] Current Thread [Next in Thread>