Re: XFS File system in trouble

From: Brian Foster <bfoster@redhat.com>
To: Leslie Rhorer <lrhorer@mygrande.net>
Cc: Eric Sandeen <sandeen@sandeen.net>,
	Kris Rusocki <kszysiu@braxis.org>,
	"Rhorer, Leslie" <Leslie.Rhorer@level3.com>,
	"xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: XFS File system in trouble
Date: Mon, 20 Jul 2015 07:17:47 -0400	[thread overview]
Message-ID: <20150720111747.GA53450@bfoster.bfoster> (raw)
In-Reply-To: <55AAF73A.4040903@mygrande.net>

On Sat, Jul 18, 2015 at 08:02:50PM -0500, Leslie Rhorer wrote:
> 
> 	I found the problem with md5sum (and probably nfs, as well).  One of the
> memory modules in the server was bad.  The problem with XFS persists.  Every
> time tar tried to create the directory:
> 
> /RAID/Server-Main/Equipment/Drive Controllers/HighPoint Adapters/Rocket 2722/Driver/RR276x/Driver/Linux/openSUSE/rr276x-suse-11.2-i386/linux/suse/i386-11.1
> 
> 	It would begin spitting out errors, starting with "Cannot mkdir: Structure
> needs cleaning".  At that point, XFS had shut down.  I went into
> /RAID/Server-Main/Equipment/Drive Controllers/HighPoint Adapters/Rocket
> 2722/Driver/RR276x/Driver/Linux/openSUSE/rr276x-suse-11.2-i386/linux/suse/
> and created the i386-11.1 directory by hand, and tar no longer starts
> spitting out errors at that point, but it does start up again at
> RR2782/Windows/Vista-Win2008-Win7-legacy_single/x64.
> 

So is this untar problem a reliable reproducer? If so, here's what I
would try to hopefully isolate a filesystem problem from something
underneath:

xfs_metadump -go /dev/md0 /somewhere/on/rootfs/md0.metadump
xfs_mdrestore -g /somewhere/on/rootfs/md0.metadump /.../fileonrootfs.img
mount /.../fileonrootfs.img /mnt/

... and repeat the test on that mount using the original tarball (if
it's on the associated fs, the version from the dump will have no data).
This will create a metadata only dump of the original fs onto another
storage device (e.g., whatever holds the root fs), restore the metadump
to a file and mount it loopback. The resulting fs will not contain any
file data, but will contain all of the metadata such as directory
structure, etc. and is otherwise mountable and usable for experimental
purposes.

If the problem is in the filesystem or "above" (as in kernel, memory
issue, etc.), the test should fail on this mount. If the problem is
beneath the fs such as somewhere in the storage stack (assuming the
rootfs storage stack is reliable), it probably shouldn't fail.

Brian

> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs