xfs
[Top] [All Lists]

Re: xfs_create looping, missing dirs/files, corrupt inode tables, etc.

To: xfs-list <linux-xfs@xxxxxxxxxxx>
Subject: Re: xfs_create looping, missing dirs/files, corrupt inode tables, etc.
From: yocum@xxxxxxxx
Date: Mon, 27 Aug 2001 09:34:54 -0500
References: <Pine.BSI.4.10.10108211902580.15144-100000@xs3.xs4all.nl> <3B865EAF.8FCA6E59@fnal.gov>
Sender: owner-linux-xfs@xxxxxxxxxxx
yocum@xxxxxxxx wrote:
> 
> Seth Mos wrote:
> 
> > > Back on topic: at least one data analyst moved about 40GB of data around
> > > last night via NFS from OSF1 to Linux using NFVv3 and there were no inode
> > > corruptions.  The kernel being used *is* 2.4.8-xfs which was compiled with
> > > gcc-2.96-85 (because I didn't get around to recompiling with kgcc yet,
> > > mkp).
> >
> > If you see it again please recompile it if you can. Or find out what's
> > going wrong with gcc 2.96.
> 
> I have, and I'm re-compiling with kgcc as we speak.  Hopefully this will fix
> the problem.
> 
> Unfortunately, there is nothing the logs that indicates a problem... gr.
> 
> As always, I'll let you know if I continue to have the problem.


*Big sigh*  

OK, I'm using my kgcc compiled 2.4.8-xfs kernel, and I'm still seeing inode
corruption, even on a "static" filesystem (i.e., mounted noatime and no
writes occuring).  

This is a very bad thing.

I'm about to punt and reformat the entire partition as XFS, and if it
happens again, then I'll have to reformat as ext2, which I really don't want
to do since it's 1.12TB.

If anyone has any ideas/patches please, please send 'em my way.  

Thanks,
Dan


-- 
Dan Yocum
Sloan Digital Sky Survey, Fermilab  630.840.6509
yocum@xxxxxxxx, http://www.sdss.org
SDSS.  Mapping the Universe.


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