On Mon, 20 Apr 2009, Theodore Tso wrote:
That's that's useful data. I wish we could make it fail more quickly on a smaller rsync, but the fact that you didn't need to reboot is definitely useful information. And this is a fresh rsync so no files were being deleted, rsync should have just been writing new files to .filename.XXXXX and then renaming the filename to filename.XXXXX when it is done, right?
That's what I'd guess. It was onto a clean filesystem, so there shouldn't be any deletions.
OK, let me think about this a little. I think we can create a patch which checks for writes to the block group descriptors and dumps a stack trace. That would allow us catch the failing code in question in the act, and maybe figure out what is going on.
Ok. Jeremy -- Jeremy Sanders <jss@xxxxxxxxxxxxx> http://www-xray.ast.cam.ac.uk/~jss/ X-Ray Group, Institute of Astronomy, University of Cambridge, UK. Public Key Server PGP Key ID: E1AAE053 -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
