UPDATE 801241 - xfsdump can cause filesystem corruption

[pv@xxxxxxxxxxxxx (dxm@xxxxxxxxxxxx)]

View Incident: 
http://co-op.engr.sgi.com/BugWorks/code/bwxquery.cgi?search=Search&wlong=1&view_type=Bug&wi=801241

 Status : open                         Priority : 1                         
 Assigned Engineer : nb                Submitter : ivanr                    
 Opened Date : 09/07/00               *Modified User : dxm                  
*Modified User Domain : engr          *Description :
QA for xfsdump/xfsrestore revealed that it is possible for
xfsdump to cause filesystem corruption.  The test involves
creating a filesystem, creating a whole buncha files, xfsdumping
them to a file somewhere, then removing all the files.  xfs_check
reports lots of inodes with zero link counts, etc.  It's probably
due to xfsdump using bulkstat on the entire fs.

The following is a script which will reliably (at least on
bruce.melbourne) produce the error.  Run it in cmd/xfs/stress -
it needs the src/fill program, and make sure you fix the

.....


==========================
ADDITIONAL INFORMATION (UPDATE)
From: dxm@engr (BugWorks)
Date: Sep 07 2000 10:25:19PM
==========================

_check_fs() should "umount $device" before running
xfs_check or xfs_repair or else "corruption" would
be expected.

I've made this change here, and still see corruption
after unmounting.