xfs
[Top] [All Lists]

REASSIGN 801241 - xfsdump can cause filesystem corruption

To: dxm@xxxxxxxxxxxx
Subject: REASSIGN 801241 - xfsdump can cause filesystem corruption
From: pv@xxxxxxxxxxxxx (dxm@xxxxxxxxxxxx)
Date: Sun, 10 Sep 2000 19:22:57 -0700 (PDT)
Cc: linux-xfs@xxxxxxxxxxx
Reply-to: sgi.bugs.xfs@xxxxxxxxxxxxxxxxx
Sender: owner-linux-xfs@xxxxxxxxxxx
Webexec: webpvupdate,pvincident
Webpv: clouds.melbourne.sgi.com
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 : dxm              *Assigned Domain : engr               
 Submitter : ivanr                     Project : xfs-linux                  
 Assigned Group : xfs-linux            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 (REASSIGN)
From: dxm@engr (BugWorks)
Date: Sep 10 2000 07:22:56PM
==========================

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