On Wed, Nov 15, 2006 at 03:36:20PM +0100, Andi Kleen wrote: > Of course this was clearly an operator error and > copying a file system into itself is clearly a sick thing > to do, but still it shouldn't cause symptoms like this. Perhaps > it points to a deeper issue. Copying is silly, moving is perhaps not. That is in fact how the in-place file system conversion tools Convertfs - http://directory.fsf.org/sysadmin/misc/ConvertFS.html and anyfs-tools - http://anyfs-tools.sourceforge.net/ work: they move files into a loop mounted filesystem, use FIBMAP to find out the logical<->physical block map, then umount the lot and move the blocks of the loop file system to their final physical destination. The assumption, of course, is that there is enough slack free space to accommodate the extra meta-data. Regards, Bill Rugolsky - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
