Submitter : ivanr Status : open
Assigned Engineer : dxm Priority : 1
*Modified Date : 09/11/00 *Modified User : jones
*Modified User Domain : tacc.cc.utexas.edu
*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 (ADD)
From: william l jones <jones@xxxxxxxxxxxxxxxxxx>
Date: Sep 11 2000 11:08:09AM
[pvnews version: 1.71]
==========================
One small observation. If I create a xfs file system and then untar a set
of files to it and then run xfs_check I get errors. They look like the same
error that I get if run xfsdump and then remove the files before running
xfs_check.
If I umount the file system and run xfs_repair I don't find any errors.
Bill Jones
|