Bug 4102 - XFS internal error xlog_valid_rec_header(2)
Summary: XFS internal error xlog_valid_rec_header(2)
Status: REJECTED INSUFFICIENT_DATA
Alias: None
Product: File System
Classification: Unclassified
Component: XFS (show other bugs)
Hardware: i386 Linux
: P2 high
Assignee: XFS Guru
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-25 20:16 UTC by Barry K. Nathan
Modified: 2007-02-17 11:59 UTC (History)
2 users (show)

See Also:
Kernel Version: 2.6.11-rc1, 2.6.11-rc2-mm1, 2.6.10-1.741_FC3
Tree: Mainline
Regression: ---


Attachments
xfs traceback from 2.6.11-rc2-mm1 (1.63 KB, text/plain)
2005-01-25 20:20 UTC, Barry K. Nathan
Details

Description Barry K. Nathan 2005-01-25 20:16:42 UTC
Distribution: Fedora Core 3

Hardware Environment: 7200RPM IDE hard disk, i386 architecture

Software Environment: XFS partition is loop mounted (i.e. it's a file stored on
another partition)

Problem Description: I have a corrupted XFS filesystem that gives me the
following error when I try to mount it:

Filesystem "loop0": XFS internal error xlog_valid_rec_header(2) at line 3516 of
file fs/xfs/xfs_log_recover.c.  Caller 0xf9452e98

This is followed by a scary-looking traceback. I assume from the appearance of
the traceback that this is something I should report as a bug. I will attach
output from 2.6.11-rc2-mm1.

Steps to reproduce:
1. Attempt to mount a particular corrupted XFS filesystem. (I would attach it
here or put it on the web or something, but it may contain sensitive information
and it's also 4GB. It gzips down to 1.8GB but that's still large relative to ISP
bandwidth bytecaps and that sort of thing. :(

Is there an XFS equivalent to e2image, or anything of the sort, that I could use
to provide more information?
Comment 1 Barry K. Nathan 2005-01-25 20:20:19 UTC
Created attachment 4468 [details]
xfs traceback from 2.6.11-rc2-mm1
Comment 2 Adrian Bunk 2006-12-07 07:49:31 UTC
Is this issue still present in kernel 2.6.19?
Comment 3 Adrian Bunk 2007-02-17 11:59:58 UTC
Please reopen this bug if it's still present with kernel 2.6.20.

Note You need to log in before you can comment on or make changes to this bug.