This function does all the needed things for changing uuid.
Signed-off-by: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
---
btrfstune.c | 57 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 57 insertions(+)
diff --git a/btrfstune.c b/btrfstune.c
index 8a5b3c2..3e308b7 100644
--- a/btrfstune.c
+++ b/btrfstune.c
@@ -29,6 +29,7 @@
#include "disk-io.h"
#include "transaction.h"
#include "utils.h"
+#include "volumes.h"
static char *device;
static int force = 0;
@@ -262,6 +263,62 @@ out:
return ret;
}
+static int change_uuid(struct btrfs_fs_info *fs_info, char *new_fsid,
+ char *new_chunk_uuid)
+{
+ int ret = 0;
+
+ /* caller should do extra check on passed uuid */
+ if (new_fsid) {
+ /* allocated mem will be freed at close_ctree() */
+ fs_info->new_fsid = malloc(BTRFS_FSID_SIZE);
+ if (!fs_info->new_fsid) {
+ ret = -ENOMEM;
+ goto out;
+ }
+ ret = uuid_parse(new_fsid, fs_info->new_fsid);
+ if (ret < 0)
+ goto out;
+ }
+
+ if (new_chunk_uuid) {
+ /* allocated mem will be freed at close_ctree() */
+ fs_info->new_chunk_tree_uuid = malloc(BTRFS_UUID_SIZE);
+ if (!fs_info->new_chunk_tree_uuid) {
+ ret = -ENOMEM;
+ goto out;
+ }
+ ret = uuid_parse(new_chunk_uuid, fs_info->new_chunk_tree_uuid);
+ if (ret < 0)
+ goto out;
+ }
+
+ /* Change extents first */
+ ret = change_extents_uuid(fs_info);
+ if (ret < 0) {
+ fprintf(stderr, "Failed to change UUID of metadata\n");
+ goto out;
+ }
+
+ /* Then devices */
+ ret = change_devices_uuid(fs_info);
+ if (ret < 0) {
+ fprintf(stderr, "Failed to change UUID of devices\n");
+ goto out;
+ }
+
+ /* Last, change fsid in super, only fsid change needs this */
+ if (new_fsid) {
+ memcpy(fs_info->fs_devices->fsid, fs_info->new_fsid,
+ BTRFS_FSID_SIZE);
+ memcpy(fs_info->super_copy->fsid, fs_info->new_fsid,
+ BTRFS_FSID_SIZE);
+ ret = write_all_supers(fs_info->tree_root);
+ }
+out:
+ return ret;
+}
+
static void print_usage(void)
{
fprintf(stderr, "usage: btrfstune [options] device\n");
--
2.3.7
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
