If we are exporting obfuscated metadata with a dirty journal, the journal is not obfuscated. So when we restore it and then replay a log, the obfuscated metadata can clash with what is in journal and corrupt the image. So, tell the user about this risk, both when exporting and importing the dump. Git tree on github: https://github.com/jtulak/xfsprogs-dev/tree/metadump Based on revision fc1d645 Jan Tulak (2): metadump: warn about corruption if log is dirty mdrestore: warn about corruption if log is dirty db/metadump.c | 3 +- mdrestore/Makefile | 4 +-- mdrestore/xfs_mdrestore.c | 84 +++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 88 insertions(+), 3 deletions(-) -- 2.1.4 -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
