Bugzilla – Bug 188
xfsdump dumps unnecessary files/inodes when doing incremental dumps
Last modified: 2008-12-31 11:52:13 CST
xfsprogs (all versions from when Noah was a boy to present) dump unnecessary files/inodes when doing incremental dumps. When files are moved/renamed (causing a directory to be changed), all files in the directory (or directories in the example below) are dumped again --- even when they are older than the dump's time stamp. For example, if you were to dump (level 0) the following: dir1/file1 dir1/file2 dir1/file3 and then after the level 0 dump do: mkdir dir2 mv dir1/file2 dir1/file1 or whatever... xfsdump will dump not only dir1 and dir2, but also all the files contained within (ie. dir1/file1, dir2/file2, dir1/file3). This is unnecessary as the file contents and inodes have not changed, and extremely annoying when a file in (say) /usr/bin gets renamed or whatever as the entire directory gets dumped. Obviously, renames of multiGB files really hurt.
Hi Chris, I remember discussing this issue with you a while back. After you mentioned this behavior, I opened an internal bug report to track it (868496). This behavior occurs on both IRIX and Linux. I'll take a look as soon as I have a chance. Mandy
Mnady, Bill - any chance you could attach the SGI PV here so that other people have a little more information if we want to look into this issue?
It seems nothing was done with the internal PV that was opened. It essentially contains the same info contained here.