Change btfrs uuid all the time

This is a workaround for a kernel bug that happens when you try to mount
the image file after creating it with cp.  It acts as if the same UUID
is already mounted, even though it isn't (anymore). Changing the UUID on
the image allows mounting it.

Can't use 'btrfstune -m' here because (for the time being) it doesn't
work on seed images. So that means that the operation is slow. It is
done more than necessary because it is done wherever made necessary by
existing code.

TODO: Change the actual behavior of the program to wait until the very
end to set seed property.  Only set -S1 when creating the patchfs or
creating the uplevel image.

1 files changed, 3 insertions, 1 deletions

diff --git a/fsmgr.hs b/fsmgr.hs
index d8e1c1d..bd4e303 100644
--- a/fsmgr.hs
+++ b/fsmgr.hs
@@ -229,6 +229,7 @@ buildInitialImage DiskImageConfig{..} mountpoint out = do
       need [parent]
       cmd_ "cp --reflink" [parent, out]
       cmd_ "btrfstune -f -S0" [out]
+      cmd_ "btrfstune -fu" [out]
       cmd_ "mkdir -p" [mountpoint]
       cmd_ "sh -c" ["if [ -e \"$0\" ]; then cp \"$0\" \"$1\"; fi", parent <.> "devices.txt", out -<.> "devices.txt"]
 
@@ -380,7 +381,8 @@ chrootImage target args =
       let mnt = tmp <.> "mnt"
       orderOnly [inp]
       cmd_ "cp --reflink=always" [inp, tmp]
-      cmd_ "btrfstune -S0 -f" tmp
+      cmd_ "btrfstune -S0 -f" [tmp]
+      cmd_ "btrfstune -fu" [tmp]
       cmd_ "mkdir" [mnt]
 
       setupLoopDevices target