Nathan,
Easy.
take stock kernel (up till 2.6.6) eventually apply evms patches, but no
need... I had it with stock kernels too
make oldconfig from included config.gz
create a raid[015] with raidtools,mdadm,evms. put files on there as
needed (as I saw that it only occurs on a / mounted md device)
boot it
hammer 10 minutes (rsync is very effective) -> you'll get:
XFS internal error XFS_WANT_CORRUPTED_GOTO at line 866 of file
fs/xfs/xfs_ialloc.c. Caller 0xffffffff8023ee04
included : config.gz, call stack trace.
If you need other info, feel free to ask. I was getting desperate ;-)
Jan
On Tue, 2004-06-01 at 11:30, Nathan Scott wrote:
> On Tue, Jun 01, 2004 at 10:32:34AM +0200, Hendrik Visage wrote:
> > On Mon, May 31, 2004 at 08:00:51AM -0700, Jord Tanner wrote:
> > >
> > > This may or may not be related, however, I had trouble running XFS on
> > > top of LVM2 on top of linux RAID0, running on gentoo 2.6.5 amd64. The
> > > problems went away after switching to JFS. I was experiencing database
> >
> > Beware that I had troubles with JFS around 2.6.0-rc? which made me test XFS
> > ;^)
> >
> > but thanx, so I'm now feeling better that I'm not the only person that'll
> > convert away from
> > XFS for the moment...
>
> We (XFS folks) would really like to hear if anyone has a reproducible
> test case that shows us how to produce this corruption. Particularly
> if its with a stock kernel from kernel.org; that'd be a _really_ huge
> help to us.
>
> thanks.
XFS_WANT
Description: Text document
config.gz
Description: GNU Zip compressed data
|