xfs
[Top] [All Lists]

RE: xfs kernel panic in 2.4.25 with mips

To: "Christoph Hellwig" <hch@xxxxxxxxxxxxx>
Subject: RE: xfs kernel panic in 2.4.25 with mips
From: "Josh Radel" <jradel@xxxxxxxxx>
Date: Wed, 23 Feb 2005 14:25:41 -0800
Cc: <linux-xfs@xxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
Thread-index: AcUQEzoy7oi5m2YFSrCq/cFHvC8GNAJ2tiiA
Thread-topic: xfs kernel panic in 2.4.25 with mips
On Fri, Feb 11, 2005 at 00:25:21 -0800, Christoph Hellwig wrote:
> 2.4.25 is from stoneage.  Please retry with 2.4.29 or even better a 
> recent 2.6 kernel.

Because of kernel-dependent hardware drivers, I can't actually use a
stock 2.4.29 or 2.6 kernel. I grabbed the fs/xfs directory (and
include/linux/dqblk_xfs.h) from the 2.4.29 tree, dropped it into the
2.4.25 tree, everything compiled, and XFS seems to work perfectly as
long as I cleanly umount the fs. While running my test program (writes
out data to disk, using XFS_IOC_RESVSP to preallocate space; I am not
flagging unwritten extents) and I suddenly cut power, maybe 1 in 5 times
the fs will not pass xfs_check (yes, I do a mount and umount first, to
replay the journal).

So I guess I have a couple questions:
        - Are the XFS changes between 2.4.25 and 2.4.29 limited to the
fs/xfs directory, or are there other kernel pieces that needed to be
fixed up? (If so, is there an easy way to figure out what those other
required changes were?)
        - Is it possible there is a journal replay problem with the
XFS_IOC_RESVSP ioctl? I haven't been able to reproduce my problems when
not using it. Is there some kind of block reclaim operation that needs
to take place but doesn't when a file isn't properly closed?

I've attached the output from "xfs_logprint -c -t -i -b" from before the
journal was replayed, and an abbreviated output from "xfs_check" from
after the journal replay.

Thanks,
Josh



-----Original Message-----
From: Christoph Hellwig [mailto:hch@xxxxxxxxxxxxx] 
Sent: Friday, February 11, 2005 12:25 AM
To: Josh Radel
Cc: linux-xfs@xxxxxxxxxxx
Subject: Re: xfs kernel panic in 2.4.25 with mips


On Thu, Feb 10, 2005 at 07:35:48PM -0800, Josh Radel wrote:
> I'm attempting to use XFS on an embedded mips32 system running the 
> 2.4.25 kernel, and am running into some kernel panics. Here are three 
> different scenarios with different (though 100% reproducible) panics. 
> In all situations, XFS is compiled into the kernel (but no other XFS 
> options, except for case (3)). I've included the kernel oops message 
> as well as the version run through ksymoops for each case at the end 
> of this message.

2.4.25 is from stoneage.  Please retry with 2.4.29 or even better a
recent 2.6 kernel.

Attachment: xfs_logprint.txt
Description: xfs_logprint.txt

Attachment: xfs_check.txt
Description: xfs_check.txt

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