Update for this topic.

After remounting the SAN to a different folder the image was still getting stuck in the dev directory. With @Tom-Elliott’s help we did an in-place upgrade to the latest Trunk. After doing this the image moved properly and there were no more issues. Thanks @Tom-Elliott!

Great, thanks. I wanted to post the question just incase there was something else in the code that needed to be know.

It is all working as advertised now

When I perform the git pull to obtain the latest Trunk, I get an error that changes need to be committed and then the git aborts. Here is the full transcript from the git pull. I have not manually made any changes to the referenced file.

root@srv01309:/opt/fogproject# git pull
remote: Counting objects: 289, done.
remote: Compressing objects: 100% (68/68), done.
remote: Total 289 (delta 177), reused 147 (delta 147), pack-reused 69
Receiving objects: 100% (289/289), 2.37 MiB | 3.87 MiB/s, done.
Resolving deltas: 100% (182/182), completed with 50 local objects.
From https://github.com/fogproject/fogproject
   456baa8..b84bae1  dev-branch -> origin/dev-branch
   8f1e322..305260c  svn        -> origin/svn
Updating b8eb6fb..b84bae1
error: Your local changes to the following files would be overwritten by merge:
        rpttmp/Hosts and Users.php
Please, commit your changes or stash them before you can merge.
Aborting

A few days ago we upgraded from v1.2 to Trunk 6050 with @Tom-Elliott help. After this upgrade we were not able to push any images that were made with v1.2. Today I updated to Trunk 6128 and still having the issue. Thanks!

Update for this topic.

After remounting the SAN to a different folder the image was still getting stuck in the dev directory. With @Tom-Elliott’s help we did an in-place upgrade to the latest Trunk. After doing this the image moved properly and there were no more issues. Thanks @Tom-Elliott!

@Tom-Elliott Thank Tom. Just sent you a chat

@Wayne-Workman I did update the GUI as well. Unfortunately I’m still getting the same result.

@Wayne-Workman I did have the dev directories set to async. I have moved the mount to /img_archive, updated the export file, and trying again.

@Wayne-Workman Here is what I have… I have an internal RAID array mounted to /images. Then I have the SAN mounted to /images/archive. (I did this because I thought it would be more friendly to FOG that way.) I can certainly remount the SAN to a different folder and give that a try. (I had had that thought as well.)

Here is what I have in my /etc/exports file:

/images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0)
/images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)
/images/archive *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=2)
/images/archive/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=3)

@Wayne-Workman Still no luck…still stuck in the dev directory.

@Wayne-Workman Yep saw that myself. Since the iscsi is going across a 1Gbit link I’m changing it to 30 and will try again. I’ll keep you posted. Thanks!